From: danny s. <ori...@gm...> - 2005-09-13 22:51:17
|
If I have made a large 20gb volume sparse, and it was at one point cleanly unmounted, 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. Cheers, Danny --=20 http://orionrobots.co.uk - Build Robots |
From: Kurt B. P. <9sj...@sn...> - 2005-09-14 16:31:15
|
danny staple wrote: > 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? I believe reading a "sparse" block will just return an all-0 block, so I don't think there's any harm done... Here's what googling for "Windows sparse file" results in: http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prkc_fil_aixf.asp So I guess I remembered correctly... -- Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria .......It might be written "Mindfuck", but it's spelt "L-A-I-N"....... np: Lyrics Born & The Poets Of Rhythm - I Changed My Mind (Spectrum) |
From: danny s. <ori...@gm...> - 2005-09-15 10:36:36
|
On 14/09/05, Kurt Bernhard Pruenner <9sj...@sn...> wrote: > danny staple wrote: > > 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? >=20 > I believe reading a "sparse" block will just return an all-0 block, so I > don't think there's any harm done... >=20 > Here's what googling for "Windows sparse file" results in: >=20 > http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en= -us/Default.asp?url=3D/resources/documentation/Windows/XP/all/reskit/en-us/= prkc_fil_aixf.asp >=20 > So I guess I remembered correctly... >=20 > -- > Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria > .......It might be written "Mindfuck", but it's spelt "L-A-I-N"....... > np: Lyrics Born & The Poets Of Rhythm - I Changed My Mind (Spectrum) >=20 >=20 >=20 Thanks. I actually did the e2fsck on the drive, and it was fine. What it found was stuff mostly to do with glibc crashing the machine during compilation (a bug with 0.6.2, but not in 0.6.3 images). I decided I needed to fsck it though after accidentally leaning a knee against my reset button (doh!) - I'm going to have to put a better guard around it! Anyway - the actual image was fine afterwards, it still booted, and the files I was interested in were still there. Better still - nothing in lost + found (I hate ending up with stuff there - its usually very bad news). So yes, this appears to be a perfectly safe operation. --=20 http://orionrobots.co.uk - Build Robots |
From: Ian B. <ib...@gm...> - 2005-09-14 17:43:30
|
From what I know about sparse files, the OS, as far as its concerned at the= =20 user level, considers the file a regular file that can be read and written= =20 to without issue. If this is the case (which I'm pretty sure it is, or else= =20 you'd see file corruption at the OS/user level) then coLinux should have no= =20 problems e2fsck'ing sparse files. In fact, I think a lot of people use=20 sparse files as a way of "compression" on colinux "filedisks" (I don't=20 really know what else to call them.. maybe block files?) Anyways, it should= =20 be safe. If coLinux can mount it, read and write to it, then you should be= =20 able to fsck it. Ian On 9/13/05, danny staple <ori...@gm...> wrote: >=20 > If I have made a large 20gb volume sparse, and it was at one point > cleanly unmounted, > 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. >=20 > 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? >=20 > It seems to be ok, but I am really worried about the interaction > between sparse and e2fsck. >=20 > Cheers, > Danny > -- > http://orionrobots.co.uk - Build Robots >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: > Tame your development challenges with Apache's Geronimo App Server.=20 > 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 > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |