lkml.org 
[lkml]   [1999]   [Nov]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: `filetype' ext2 feature causes dump to SEGV
From
Date
Stelian Pop <pop@cybercable.fr> writes:

> I was wondering why dump uses
> direct disc access (open and read directly the direct, indirect and
> doubly indirect blocks), instead of using the associated e2fsprogs
> library functions. Did Rémy done this because the functions didn't
> exist at this time or was this for performance reasons ?

I think it was because Linux dump was (more or less) a port from the
Berkeley FFS equivalent, which did this (and furthermore, did it to
the raw device, so dumping a non-quiescent filesystem was guaranteed
to be trouble). I'm pretty sure the BSD version did it for (a)
performance, and (b) so it could easily keep track of inode
information to make incremental restores easier (not that you couldn't
do it with stat(), but that's yet another syscall to slow things
down).

-Doug
--
Doug McNaught doug@mcnaught.org http://www.mcnaught.org/~doug

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:55    [W:0.067 / U:0.944 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site