Linda Walsh composed on 2015-09-20 15:35 (UTC-0700):
Felix Miata wrote:
John M Andersen composed on 2015-09-20 14:49 (UTC-0700):
Felix Miata wrote:
# ls -l /mnt/out -rw-rw-rw- 1 root root 120 Apr 16 2014 /mnt/out
What are the permissions of /mnt?
With /dev/md1 mounted to it: drwxr-xr-x 27 root root 2048 Apr 22 2014
Without /dev/md1 mounted to it: drwxr-xr-x 2 root root 2048 Sep 25 2014
---- have you tried a 'strace' and maybe ltrace on the rm command to see if it is failing on a system or a library call?
Not things I can make much sense of: http://fm.no-ip.com/Tmp/SUSE/132/strace-rmr.txt
Is there some way in the md driver might be mounting the devices read only, like if the following was stuck?)...
As files are able to be written to, I have no idea how such could be.
md_mod.start_ro=1
Is this something to try adding to kernel cmdline?
/sys/module/md_mod/parameters/start_ro This tells md to start all arrays in read-only mode. This is a soft read-only that will automatically switch to read-write on the first write request. However until that write request, nothing is written to any device by md, and in particular, no resync or recovery operation is started.
Or am I understanding it is ONLY a few files that are affected?
Can you create/delete other files in root?
Cannot remove or rename those that exist. Cannot create new. (e.g. touch newfile fails) Cannot move any there now to a subdir or to a different filesystem.
Can you read from those files?
Can read and write those that do exist....
How about write to them i.e. dd if=/dev/null of=/mnt/troublesome_file or just echo >/mnt/troublesome file?
mcedit works on the text files there. Subdirs and files can be added to and removed from the non-removable dirs.
Any extended ACL's or any other non-linux default security system installed?
Nothing knowingly done. If I've ever used ACLs, it wasn't intentional. What can I check? Possibly I have found what looks like a clue. This is a partial list of its content gathered while booted from it: -rw-r--r-- 1 root root 88139 Apr 15 2014 .readahead drwxr-xr-x 2 root root 2048 Sep 27 2013 mnt drwxrwxr-x 3 root root 2048 Sep 20 18:49 nfs -rw-rw-rw- 1 root root 120 Apr 16 2014 out -rw-r--r-- 1 root root 340668 Apr 16 2014 shutdown-log-big31-131.txt -rw-r--r-- 1 root root 66462 Sep 20 16:05 shutdown-log.txt drwxrwxr-x 2 root root 2048 Sep 19 14:06 smbmnt I have no recollection what could be responsible for the creation of shutdown-log.txt. From the date of the older one, it must have had to do with some kind of diagnostic request in a forum or Bugzilla. Oh, here: http://lists.opensuse.org/opensuse/2014-04/msg00436.html That reminds me, 13.1 installations randomly take an unusually long time to reboot, typically following applying updates, but not always. When I reboot it (13.1), its content is entirely replaced - I stripped all but the last few lines from it before rebooting, and they were gone afterward. The others either I'm responsible for, or I know what is or was. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org