From: Eric Sandeen <sandeen@redhat.com>
To: Matteo Croce <technoboy85@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Massive filesystem corruption
Date: Sat, 20 Dec 2008 21:23:16 -0600 [thread overview]
Message-ID: <494DB6A4.9010402@redhat.com> (raw)
In-Reply-To: <200812210305.49271.technoboy85@gmail.com>
Matteo Croce wrote:
> debugfs is new to me, have you some docs for me to read?
sure, "man debugfs"
-Eric
next prev parent reply other threads:[~2008-12-21 3:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 5:49 (resend) extent header problems following shrink with resize2fs Paul Collins
2008-12-23 6:18 ` Theodore Tso
2008-12-20 18:14 ` Massive filesystem corruption Matteo Croce
2008-12-20 19:27 ` Eric Sandeen
2008-12-21 2:05 ` Matteo Croce
2008-12-21 3:23 ` Eric Sandeen [this message]
2008-12-21 5:09 ` Nick Dokos
2008-12-26 3:57 ` Theodore Tso
2008-12-25 7:18 ` (resend) extent header problems following shrink with resize2fs Paul Collins
2008-12-25 13:09 ` Theodore Tso
2008-12-26 4:14 ` Theodore Tso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=494DB6A4.9010402@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=technoboy85@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).