Re: [Dump-users] Can't read next inode ...

[Stelian P. <st...@po...>]

Le jeudi 21 août 2008 à 13:57 -0700, Perry Hutchison a écrit :
> > > What would you think of adding some options:
> > > 
> > >   -D filesystem
> > [...]
> > >   -i
> > [...]
> > >   -X
> > [...]
> >
> > I'm confused. To what program do you intend to pass those options ?
> > (Linux) dump manpage or (my local copy of) losetup manpage do not
> > mention those.
> 
> I'm suggesting adding those capabilities to dump.

Ok, got it now.

> I would expect -D to be fairly easy,

indeed

>  and -i also provided it's
> not necessary to have read the Nth inode block in order to find
> the (N+1)th inode block.

dump used e2fsprogs' ext2fs_block_iterate2() to iterate over the blocks
of one inode. I'm not sure (at least it is not documented) that
ext2fs_block_iterate2() allows the behaviour you're searching for.

>   -X might be more troublesome, depending
> on how much block accounting dump is already doing.

Dump does not do any block accounting, it relies on e2fsprogs functions
to obtain the block numbers it needs to save.

Stelian.
-- 
Stelian Pop <st...@po...>