Re: Damaged file system
From: Trent Buck (geragohpx_at_tznvy.pbz)
Date: 01/22/05
- Next message: Chuck Forsberg: "Searching for articles in newsgroups"
- Previous message: tom: "Damaged file system"
- In reply to: tom: "Damaged file system"
- Next in thread: Trent Buck: "Re: Damaged file system"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 22 Jan 2005 02:42:09 GMT
Up spake tom:
> Inside my working directory (i.e. on the second disk) suddenly new files or
> directories exist out of the blue, their name is usually something like
> "FSCK0000.REN". This is strange enough, but sometimes, when such a creation
> is a directory, recursive trees exist in such a file, containing the whole
> tree structure of my second disk. The attempt to delete these directories
> is refused. The only way to set the system back to normal is a reboot with
> Windows and a reformatting of the whole disk.
fsck(1) is the name of the unix FileSystem ChecKer (kinda like scandisk).
I suspect that fsck created these files because the disk / filesystem is
damaged, and fsck has rescued these files. fsck can't tell what the
names were, so it gives them generic ones.
Alternately, it could be that fsck is unreasonably confused by something
on the vfat filesystem, such as if you have a filename with a space.
You can prevent fsck from checking this drive by finding the relevant
line in /etc/fstab, e.g.
/dev/hdb1 /data vfat defaults 0 1
and change the last column to "0" (it should be "1" at the moment).
If you do this, underlying problems with the disk / filesystem won't be
discovered, so I advise you to also look into *why* fsck is getting
upset, such as by running fsck manually or going through the logs
created when fsck was last run automatically.
> I don't know if this has the same cause, but there is also another problem
> frequently occuring in the file structure: several files suddenly have new
> names, e.g. "program1.sml" suddenly becomes "prog_am.s?l" or something
> similar.
>From a technical perspective, the vfat filesystem is crap. If you don't
use that data under windows, consider using ext3 or another Linux
filesystem.
If you need to access that filesystem under Windows, you could get the
Windows ext2 driver, which allows windows to read ext3-formatted
filesystems. This would be preferable to a vfat filesystem, but I've
never tried it so I can't vouch for its stability.
-- -trent SCSI is *not* magic. There are fundamental technical reasons why it is necessary to sacrifice a young goat to your SCSI chain now and then.
- Next message: Chuck Forsberg: "Searching for articles in newsgroups"
- Previous message: tom: "Damaged file system"
- In reply to: tom: "Damaged file system"
- Next in thread: Trent Buck: "Re: Damaged file system"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
