From what I know about sparse files, the OS, as far as its concerned at
the user level, considers the file a regular file that can be read and
written to without issue. If this is the case (which I'm pretty sure it
is, or else you'd see file corruption at the OS/user level) then
coLinux should have no problems e2fsck'ing sparse files. In fact, I
think a lot of people use sparse files as a way of "compression" on
colinux "filedisks" (I don't really know what else to call them.. maybe
block files?) Anyways, it should be safe. If coLinux can mount it, read
and write to it, then you should be able to fsck it.
If I have made a large 20gb volume sparse, and it was at one point
is it safe to use e2fsck on it? It was an ext2 image, and was resized
to be larger first, then mksparse used to compact it.
I have already foolishly started e2fsck, and suddenly thought the the
sparse flag may cause blocks in many inodes to be unreadable (and
incorrectly identified as bad)- or have I misunderstood how the NT
sparse flag operates?
It seems to be ok, but I am really worried about the interaction
between sparse and e2fsck.
http://orionrobots.co.uk - Build Robots
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
coLinux-users mailing list