From: Theodore Tso <tytso@MIT.EDU>
To: Paul Collins <paul@burly.ondioline.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: (resend) extent header problems following shrink with resize2fs
Date: Tue, 23 Dec 2008 01:18:33 -0500 [thread overview]
Message-ID: <20081223061833.GQ23723@mit.edu> (raw)
In-Reply-To: <87abanbfvo.fsf@burly.wgtn.ondioline.org>
On Tue, Dec 23, 2008 at 06:49:15PM +1300, Paul Collins wrote:
> (resending without gipped attachment)
>
> Yesterday I created a ~464GB ext4 volume and copied about 107GB of music
> files onto it. Then I decided that I wanted to use half of the disk for
> something else, so last night I resized the ext4 filesystem to ~232GB
> and recreated the partitions to suit. This morning I wrote some new
> files to the ext4 filesystem, which went fine. Then I installed a new
> music player, which wanted to scan all of the files on the disk. It
> reported being unable to read some files, and there's rather a lot of
> this sort of thing in dmesg (see also http://ondioline.org/~paul/e4dmesg.gz):
Yeah, resize2fs needs to be fixed to handle extents correctly. At the
moment it can screw them up pretty badly. I'll log this as a bug to
resize2fs; thanks for reporting it, and I hope you didn't suffer any
permanent data loss.
Regards,
- Ted
next prev parent reply other threads:[~2008-12-23 6:18 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 [this message]
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
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=20081223061833.GQ23723@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=paul@burly.ondioline.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.