[opensuse] hOW TO REMOVE A FILE THAT IS CONSIDERED "READ ONLY FILE SYSTEM"
I have dumped huge directories (uncompressed) from SuSE 10.3 onto my external hard drive (SEAGATE which is only 25% full after such operation). I have tar-red the huge files. But when I try to gzip the tar-archive the system refuses to do so because such an archive is considered a "read-only file system". Even as root (#su -) I cannot remove the archive. If I try to move it to my computer hard drive then a copy is made but it does not get removed from the SEAGATE external drive because of the same reason. Even as root I am not allowed to change the access rights (#chmod a=+wr <archive-name>) nor I am allowed to change the file owner (#chown) even if it belongs to me as a user ... I am out of ideas about how to remove/delete such a file ... it is a nightmare ! Thanks to everybody who can help me out of my misery. Maura -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Maura Monville wrote:
I have dumped huge directories (uncompressed) from SuSE 10.3 onto my external hard drive (SEAGATE which is only 25% full after such operation). I have tar-red the huge files. But when I try to gzip the tar-archive the system refuses to do so because such an archive is considered a "read-only file system".
Uh, a _file_ can be read-only, but it would take a few more steps to make it a read-only _file-system_. It sounds like your external drive has somehow become read-only. I can't think of how - you did manage to write the tar-file to it.
Even as root (#su -) I cannot remove the archive.
You could try remounting your external drive as rw - mount -o rw,remount <yourdrive> <yourmountpoint> -- Per Jessen, Zürich (15.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On June 9, 2009 04:34:23 am Per Jessen wrote:
You could try remounting your external drive as rw -
mount -o rw,remount <yourdrive> <yourmountpoint>
That should be mount -o remount,rw <yourdrive> <yourmountpoint> -- Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Don Raboud wrote:
On June 9, 2009 04:34:23 am Per Jessen wrote:
You could try remounting your external drive as rw -
mount -o rw,remount <yourdrive> <yourmountpoint>
That should be
mount -o remount,rw <yourdrive> <yourmountpoint>
Don, they're keyword paraneters, not positional. Either way works. /Per -- Per Jessen, Zürich (19.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-06-09 at 12:34 +0200, Per Jessen wrote:
Maura Monville wrote:
Subject: Re: [opensuse] hOW TO REMOVE A FILE THAT IS CONSIDERED "READ ONLY FILE SYSTEM"
Please, don't SHOUT.
I have dumped huge directories (uncompressed) from SuSE 10.3 onto my external hard drive (SEAGATE which is only 25% full after such operation). I have tar-red the huge files. But when I try to gzip the tar-archive the system refuses to do so because such an archive is considered a "read-only file system".
Uh, a _file_ can be read-only, but it would take a few more steps to make it a read-only _file-system_. It sounds like your external drive has somehow become read-only. I can't think of how - you did manage to write the tar-file to it.
It happens when the kernel discovers a corruption or has an Oops or similar. The kernel switches the affected filesystem to read only to impede further damage. It happened to me the other day. Proof of this could be found in the kernel log. The proper procedure is umounting, running an fsck on that filesystem, then mounting again. And then, I would copy the file it was writing to at the moment of failure. Ie, I would rerun the backup, or at least, fully check it.
You could try remounting your external drive as rw -
mount -o rw,remount <yourdrive> <yourmountpoint>
That should fail, too. Hopefully ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkouTZwACgkQtTMYHG2NR9UuhwCbBtiOTrUSoAnNzWT5DyzXgljV TIAAnjm2WJhHwEVilBJZ/x0q6OFaEuZU =QEFB -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Tuesday, 2009-06-09 at 12:34 +0200, Per Jessen wrote:
Maura Monville wrote:
Subject: Re: [opensuse] hOW TO REMOVE A FILE THAT IS CONSIDERED "READ ONLY FILE SYSTEM"
Please, don't SHOUT.
I have dumped huge directories (uncompressed) from SuSE 10.3 onto my external hard drive (SEAGATE which is only 25% full after such operation). I have tar-red the huge files. But when I try to gzip the tar-archive the system refuses to do so because such an archive is considered a "read-only file system". Uh, a _file_ can be read-only, but it would take a few more steps to make it a read-only _file-system_. It sounds like your external drive has somehow become read-only. I can't think of how - you did manage to write the tar-file to it.
It happens when the kernel discovers a corruption or has an Oops or similar. The kernel switches the affected filesystem to read only to impede further damage.
It happened to me the other day.
Proof of this could be found in the kernel log.
The proper procedure is umounting, running an fsck on that filesystem, then mounting again.
And then, I would copy the file it was writing to at the moment of failure. Ie, I would rerun the backup, or at least, fully check it.
You could try remounting your external drive as rw -
mount -o rw,remount <yourdrive> <yourmountpoint>
That should fail, too. Hopefully ;-)
Good to know that "gory little detail". Thanks for the concise what- and how- summary, Carlos. One other possibility to consider, if even this procedure doesn't bring satisfaction, is that perhaps, if the drive has been handled, that some sort of hardware read-only switch or jumper has been altered. But Carlos' interpretation seems quite probable, as well. Could be either. I'd check/do both. Short of reading the kernel source tree, is there someplace where one can find more details of kernel behavior under duress, such as what Carlos has described? I'm thinking something a bit more comprehensive than release notes, but not as dry as a complete bugzilla list. --Dan G. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-06-09 at 10:22 -0400, Dan Goodman wrote:
Good to know that "gory little detail". Thanks for the concise what- and how- summary, Carlos.
One other possibility to consider, if even this procedure doesn't bring satisfaction, is that perhaps, if the drive has been handled, that some sort of hardware read-only switch or jumper has been altered.
Could be...
But Carlos' interpretation seems quite probable, as well. Could be either. I'd check/do both.
Short of reading the kernel source tree, is there someplace where one can find more details of kernel behavior under duress, such as what Carlos has described? I'm thinking something a bit more comprehensive than release notes, but not as dry as a complete bugzilla list.
Not that I know. It is... know how, experience, what you have seen before or heard from someone or read... unless you happen to be a kernel developer and then you really /know/. In Linux, there is not a book you can read and know everything, and that knowledge be and stay current. Unfortunately. Documentation is distributed, somewhat difficult to find, and changes rapidly. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkou4GkACgkQtTMYHG2NR9WS0wCeJ7IBWakPNJWx13XBRCR6cNCC WcAAn3Q7gpL5Mz6p4eHySAOKZC4WDNIP =fyZw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Tuesday, 2009-06-09 at 10:22 -0400, Dan Goodman wrote:
...
Short of reading the kernel source tree, is there someplace where one can find more details of kernel behavior under duress, such as what Carlos has described? I'm thinking something a bit more comprehensive than release notes, but not as dry as a complete bugzilla list.
Not that I know.
It is... know how, experience, what you have seen before or heard from someone or read... unless you happen to be a kernel developer and then you really /know/.
In Linux, there is not a book you can read and know everything, and that knowledge be and stay current. Unfortunately. Documentation is distributed, somewhat difficult to find, and changes rapidly.
Pretty much as I expected, but it does raise two questions: (1) Am I (fill in the blank) to want to try to read and comprehend kernel code; and (2) what is the current state of attempts to build a central repository of Linux docs, whether it is tldp.org or something else, or have people given up on the idea? In the meantime, I read this list and glance at the bugs list, and learn a bit here and a bit there. --Dan G. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 09 June 09, Carlos E. R. wrote:
On Tuesday, 2009-06-09 at 12:34 +0200, Per Jessen wrote:
Maura Monville wrote:
Subject: Re: [opensuse] hOW TO REMOVE A FILE THAT IS CONSIDERED "READ ONLY FILE SYSTEM"
Please, don't SHOUT.
Friggin' hypocrite. -- Those who see no difference between people legally immigrating to the US and people who come here illegally must likewise see no difference between consensual sex and rape. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
JB2 wrote:
On 09 June 09, Carlos E. R. wrote:
On Tuesday, 2009-06-09 at 12:34 +0200, Per Jessen wrote:
Maura Monville wrote:
Subject: Re: [opensuse] hOW TO REMOVE A FILE THAT IS CONSIDERED "READ ONLY FILE SYSTEM" Please, don't SHOUT.
Friggin' hypocrite.
I think he's trying to explain that all caps is shouting. -- Tony Alfrey tonyalfrey@earthlink.net "I'd Rather Be Sailing" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-06-09 at 10:40 -0700, Tony Alfrey wrote:
Please, don't SHOUT.
Friggin' hypocrite.
I think he's trying to explain that all caps is shouting.
Exactly. But further down there was my reply to the OP problem; whereas when JB2 rebukes somebody for top-posting he/she doesn't. He thinks I did the same as he/she did, so he/she says I'm an hypocrite. Nice. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkouwtUACgkQtTMYHG2NR9XECACfYeUliMye5tFfBo7bsv55KbzO NnwAnR2hf2Zp6Ji/1NYM97yumsAhR6f8 =JXB0 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday, 2009-06-09 at 10:40 -0700, Tony Alfrey wrote:
Please, don't SHOUT.
Friggin' hypocrite.
I think he's trying to explain that all caps is shouting.
Exactly. But further down there was my reply to the OP problem; whereas when JB2 rebukes somebody for top-posting he/she doesn't. He thinks I did the same as he/she did, so he/she says I'm an hypocrite.
Nice.
It _was_ pointed out subsequently that the use of caps was characteristic of a capslock key being down. Taking on the role of netiquette admin can tweak people's heads, especially on this list. However, your answer to the OP problem looked quite helpful, so it's not as if you were simply playing net police. -- Tony Alfrey tonyalfrey@earthlink.net "I'd Rather Be Sailing" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 09 June 09, Tony Alfrey wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday, 2009-06-09 at 10:40 -0700, Tony Alfrey wrote:
Please, don't SHOUT.
Friggin' hypocrite.
I think he's trying to explain that all caps is shouting.
Exactly. But further down there was my reply to the OP problem; whereas when JB2 rebukes somebody for top-posting he/she doesn't. He thinks I did the same as he/she did, so he/she says I'm an hypocrite.
Nice.
It _was_ pointed out subsequently that the use of caps was characteristic of a capslock key being down. Taking on the role of netiquette admin can tweak people's heads, especially on this list. However, your answer to the OP problem looked quite helpful, so it's not as if you were simply playing net police.
But doing *both* makes it all okay, right? You too, are a hypocrite. Carlos never even bothered to ask or find out if I first ask people not to top-post *off-list*...he simply ASS-u-med. I suppose as long as the rest of you elitist asses think that as long as following your rules as stated in your paragraph above is good, then it's okay for only you people to do it. Gotta love those who live behind double standards, it must give you all warm, fuzzy feelings. -- "Politicians and diapers need to be changed regularly -- and for the same reason." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 10 Jun 2009 12:11:19 -0500, JB2 wrote: [bunch of stuff snipped] This should really go to the off-topic list now. Or private e-mail. The openSUSE users list isn't the place for flamewars. Jim -- Jim Henderson Please keep on-topic replies on the list so everyone benefits -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
JB2 wrote:
On 09 June 09, Tony Alfrey wrote:
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tuesday, 2009-06-09 at 10:40 -0700, Tony Alfrey wrote:
Please, don't SHOUT. Friggin' hypocrite. I think he's trying to explain that all caps is shouting. Exactly. But further down there was my reply to the OP problem; whereas when JB2 rebukes somebody for top-posting he/she doesn't. He thinks I did the same as he/she did, so he/she says I'm an hypocrite.
Nice. It _was_ pointed out subsequently that the use of caps was characteristic of a capslock key being down. Taking on the role of netiquette admin can tweak people's heads, especially on this list. However, your answer to the OP problem looked quite helpful, so it's not as if you were simply playing net police.
But doing *both* makes it all okay, right? You too, are a hypocrite. <snip>
Sir, I do not know what is bothering you, but your ad hominem, antagonistic approach to discourse is simply not appropriate for this list or any other form of civilized interaction. My comments were intended to be constructive criticism to Carlos' approach to dealing with all caps posting. Then you come out from left field ranting unintelligibly about top-posting and double standards. You will benefit from some self-examination of your behavior. -- Tony Alfrey tonyalfrey@earthlink.net "I'd Rather Be Sailing" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
JB2 wrote:
On 09 June 09, Carlos E. R. wrote:
On Tuesday, 2009-06-09 at 12:34 +0200, Per Jessen wrote:
Maura Monville wrote:
Subject: Re: [opensuse] hOW TO REMOVE A FILE THAT IS CONSIDERED "READ ONLY FILE SYSTEM"
Please, don't SHOUT.
Please, don't chastise people for typo's. Even if you ARE so perfect you never make any. You don't recognize a flipped capslock when you see it?
Friggin' hypocrite.
Indeed. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-06-09 at 12:19 -0500, JB2 wrote:
On 09 June 09, Carlos E. R. wrote:
On Tuesday, 2009-06-09 at 12:34 +0200, Per Jessen wrote:
Maura Monville wrote:
Subject: Re: [opensuse] hOW TO REMOVE A FILE THAT IS CONSIDERED "READ ONLY FILE SYSTEM"
Please, don't SHOUT.
Friggin' hypocrite.
Ah, how nice... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkouweAACgkQtTMYHG2NR9XnjgCfQzZHJAUvQay+H4Gi9H/6chl7 8pcAnjyRpHHXXegC/3G8YPG7N7p0baKb =LE4W -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Brian K. White -
Carlos E. R. -
Dan Goodman -
Don Raboud -
JB2 -
Jim Henderson -
Maura Monville -
Per Jessen -
Tony Alfrey