Toni Müller wrote:
> Yuck. I talked to the user, and he's fine with shipping the data, but
> somehow, it has become unclear which machine is effected, and
> furthermore, the user dislikes loss of operation to find out. I'll try
> to talk to him again to make the data finally available.
>
> Sorry f
On 04/05/2012 12:09 AM, Jonathan Nieder wrote:
> Toni Müller wrote:
>> the file system is still available, but I need to check with the user if
>> I can ship his data offsite
>
> Did you find out?
Yuck. I talked to the user, and he's fine with shipping the data, but
somehow, it has become unclear
Toni Müller wrote:
> On 11/27/2011 05:06 AM, Jonathan Nieder wrote:
>> Do you still have the corrupted filesystem available? It might be
>> interesting to try to do a post-mortem analysis on it --- please see
>> the RAW IMAGE FILES section of e2image(8) and let us know if that
>> will be possible
Toni Müller wrote:
> I don't see -Q mentioned in the man page. You mean, I should backport
> the e2image from Wheezy (where it first seems to appear) to Etch (the
> affected system)? Any gotchas that I should be aware of?
Well, whatever's most convenient. (That might be to just use "-r" ---
the
On 11/29/2011 12:38 PM, Jonathan Nieder wrote:
> Jonathan Nieder wrote:
>> Note that "e2image -r" only writes metadata (using holes in place of
>> actual data), so "e2image -r - | bzip2 > corrupted.e2i.bz2"
>> may not be too large if the metadata is not too complex. If you want
>> to avoid reveal
Jonathan Nieder wrote:
> Note that "e2image -r" only writes metadata (using holes in place of
> actual data), so "e2image -r - | bzip2 > corrupted.e2i.bz2"
> may not be too large if the metadata is not too complex. If you want
> to avoid revealing filenames, the "-s" option to e2image can help.
Toni Müller wrote:
> the file system is still available, but I need to check with the user if
> I can ship his data offsite, and it would be a large file (~115GB).
Note that "e2image -r" only writes metadata (using holes in place of
actual data), so "e2image -r - | bzip2 > corrupted.e2i.bz2"
may
Hi Jonathan,
On 11/27/2011 05:06 AM, Jonathan Nieder wrote:
> Do you still have the corrupted filesystem available? It might be
> interesting to try to do a post-mortem analysis on it --- please see
> the RAW IMAGE FILES section of e2image(8) and let us know if that
> will be possible.
the file
Hi Toni,
Toni Mueller wrote:
> On Mon, 31.05.2010 at 20:27:02 +0200, Toni Mueller wrote:
>> # fsck -p /dev/mapper/uv0-srv
>> fsck 1.41.3 (12-Oct-2008)
>> /dev/mapper/uv0-srv contains a file system with errors, check forced.
>> /dev/mapper/uv0-srv: Problem in HTREE directory inode 20742394: node
9 matches
Mail list logo
