[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Failures they e2fsck doesn't find



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jörg Sommer wrote:
> 
>>the output of e2image -r /dev/hdXX - | bzip2 > hdXX.img.gz?
> 
> Ehmm, no. My PGP-Key is on this filesystem and I don't have space to
> create the image. Can I extract only parts?

for the sake of correctness, man 8 e2image tells us:

This [the command above] will only send the metadata information, without
any data blocks.  However, the filenames in the directory blocks can
still reveal information about the contents of the filesystem that the bug
reporter may wish  to  keep  confidential. To address  this concern, the
- -s option can be specified.  This will cause e2image to scramble directory
entries and zero out any unused portions of the directory blocks before
writing them to the image file.

being curious about e2image by myself i just had to test it on a loop-aes
mounted 4GB ext3 partition, the product is a 6,2MB loop6.img.gz...

Christian.
- --
BOFH excuse #21:

POSIX compliance problem

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCJyGDC/PVm5+NVoYRAotiAJ48aFK5B3bWyLVCO/MfekvFZtJcaQCgseWb
pdjz1bm6LUXVV6h6OHtR0f8=
=4eYf
-----END PGP SIGNATURE-----


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]