Re: FAT32 weirdness
- From: Jim Showalter <jshowalter@xxxxxxxxxxxxxx>
- Date: Tue, 21 Nov 2006 04:41:49 GMT
Doug Freyburger wrote:
Jim Showalter wrote:
How could making one file read only have caused the entire file system
to become read only?
The usual reason for going read-only is a hardware failure and the
filesystem layer making the entire filesystem R/O. Then a
remount to turn it back to R/W. Note that the error message does
include "file system".
You are right. I found since that the disk had some errors, so I
moved everything to a new disk. I consider myself very lucky, as I
didn't even need to use my daily backups and didn't lose so much as
one file!
You did double check that you could create files in other directories
or with another name, right?
I'm not sure of your meaning here. The entire file system on the drive
mounted on /e would become read-only. And if I can't create a file by
one name, why might another succeed?
Cheers!
droid
--
I know what I believe. I will continue to articulate what I believe and
what I believe - I believe what I believe is right. --George W. Bush
* Now that's articulate! *
.
- Follow-Ups:
- Re: FAT32 weirdness
- From: Doug Freyburger
- Re: FAT32 weirdness
- References:
- FAT32 weirdness
- From: Jim Showalter
- Re: FAT32 weirdness
- From: Jim Showalter
- Re: FAT32 weirdness
- From: Doug Freyburger
- FAT32 weirdness
- Prev by Date: Re: FAT32 weirdness
- Next by Date: Problem compiling binutils
- Previous by thread: Re: FAT32 weirdness
- Next by thread: Re: FAT32 weirdness
- Index(es):
Relevant Pages
|