January 28, 201214 yr I am trying to do a rm -r on a folder on disk11 but it says it is a read-only file system. Strange that I can remove files on every other disk with no issues. What is the issue?
January 28, 201214 yr See here: http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems
January 28, 201214 yr I'm not sure you need to go to the extent of a file system check yet... you may simply have the file opened by another process. Or you can use from the command prompt "rm -rf <fold name>" which tells linux to force the delete...this may still fail if the file is open by another processes.
January 28, 201214 yr I'm not sure you need to go to the extent of a file system check yet... you may simply have the file opened by another process. Or you can use from the command prompt "rm -rf <fold name>" which tells linux to force the delete...this may still fail if the file is open by another processes. linux/unix have ALWAYS let you remove a file, even if open for reading and/or writing by another process. In fact, many programs took advantage of this by opening a temp file for read/write, removing it, and then it magically goes away when the program ends. (The last reference to the blocks holding the data, when removed, frees the blocks. An open file handle counts as a reference, just like a directory pointer) Your file system has probably been marked as read-only due to file-system corruption to prevent further corruption.
January 28, 201214 yr Thanks for the reminder Joe. I havent programmed in Linux for so long i forgot that "everything" is basically a file/pointer. Sent from my SGH-I727R using Tapatalk
January 29, 201214 yr So is there a fix for it? yes, it was described (with a link) in the second post in this thread.
January 29, 201214 yr Author Great... I am going to try that tomorrow. Does the whole array need to be down to just fix disk11?
January 29, 201214 yr Its in the instructions - bring the array down, ensure each disk your checking is not mounted, etc.
January 29, 201214 yr Its in the instructions - bring the array down, ensure each disk your checking is not mounted, etc. Actually, no, the array must be started to check via the /dev/mdX devices. You would NOT stop the array. You would stop SAMBA, as in the instructions, since the drives need to have nothing accessing them to be un-mounted.
January 30, 201214 yr Author The procedure worked great. The drive is back to normal now. Thanks again for the help.
Archived
This topic is now archived and is closed to further replies.