Comment 3 for bug 1329288

I'm afraid I was running fsck by hand, and I copied that from the
terminal before moving on to further fsck runs (that didn't explode
like that; I've now got what seems to be all of the data from the disk
in lost+found, dredging through that to see if the backups I don't
have elsewhere are still there).

This was on an ext4 partition that had gotten mangled by an
interrupted gparted run (running gparted over USB turns out to not be
that good an idea).

No logs other than that.

On 12 June 2014 17:07, Theodore Ts'o <email address hidden> wrote:
> Can you get me the fsck transcript for this run in question? It might
> be in /var/log/fsck
>
> Failing that, can you tell me what file system it was checking? Can
> you run e2fsck by hand, and try to reproduce the failure, and grab the
> e2fsck output when you do re-run it?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1329288
>
> Title:
> fsck SEGV
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1329288/+subscriptions