On Mon, Jan 17, 2005 at 10:45:59PM +0100, Walter Hofmann wrote:
> I have a backup, so I could theoretically do as you say. However: I
> would have to rename the directories. Will renaming all files to random
> names (of the same length, say) disturb the filesystem structure enough
> to make the image useless?
As long as you rename the files one at a time, keeping the lengths
constant, that shouldn't disturb the filesystem structure at all.
I've thought about adding a "scramble" option to e2image -r, which
randomly scrambles directory entries while keeping the name lengths
and inode numbers constant, but I've never had the time to do it.
> The filesystem size is 60GB. Even if bzip2 does wonders this will
> take a while & lots of space.
Well, remember that e2image -r drops all of the data blocks, so all
that bzip2 will be compressing will be a huge number of zero-filled
blocks (which don't take much space :-) and the metadata blocks.
The command "e2image -r /dev/hda2 - | bzip2 > hda2.e2i.bz2" should
create a save.bz2 file that should be reasonably sized. For example,
given one 128 meg filesystem, the resulting e2i.bz2 file was only
353k. For my 45 gig filesystem, the resulting e2i.bz2 file was about
19 megs.
> Maybe there are easier ways to find
> the problem. Would strace'ing or ltrace'ing resize2fs be of any
> help?
The output of "resize2fs -d 255" might be helpful, but there's no
guarantee that'll show me what's happening.
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
