From: Eric Sandeen <sandeen@redhat.com>
To: John Jolly <john.jolly@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Failure of resize2fs past 4TB
Date: Wed, 27 Mar 2013 22:57:25 -0500 [thread overview]
Message-ID: <5153BFA5.9090404@redhat.com> (raw)
In-Reply-To: <CAN=xW0bhw41-NNqWnDfqk0SbM6xymrhuL9WONQKefC=PsHg5GQ@mail.gmail.com>
On 3/27/13 10:44 PM, John Jolly wrote:
> All,
>
> I recently had a major data loss when expanding an LVM logical volume
> past 2TB in size. I have preserved the 2.25TB just in case I might be
> able to recover some data. But this backup is not my reason for
> writing.
>
> I have done several tests and these are the results. First the error
> condition, where I create a 1GB file system, expand the volume to 2TB,
> resize the file system and have it become corrupted:
I checked the recent code in the master & pu branches of git, and the
same problem persists.
...
> I know it is unusual to start so small and expand like this, but I
> doubt I am the only one to have experienced this. How could I have
> prepared my small 1GB file system so that it would be able to handle
> an expansion past 2TB? Any help would be appreciated.
not sure; you haven't done anything wrong, this simply looks like
a resize bug, of which there have been a few lately I'm afraid.
-Eric
> Regards,
> --
> John Jolly - john.jolly@gmail.com - http://john.jolly.name
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-03-28 3:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 3:44 Failure of resize2fs past 4TB John Jolly
2013-03-28 3:57 ` Eric Sandeen [this message]
2013-03-28 11:55 ` Theodore Ts'o
2013-04-01 0:43 ` [PATCH 0/4] e2fsprogs: fix off-line resizing of small ext4 file systems Theodore Ts'o
2013-04-01 0:44 ` [PATCH 1/4] resize2fs: fix off-line resize of file systems with flex_bg && !resize_inode Theodore Ts'o
2013-04-01 0:44 ` [PATCH 2/4] mke2fs: don't display bigalloc/quota fs feature warnings in quiet mode Theodore Ts'o
2013-04-01 0:44 ` [PATCH 3/4] tests: create crcsum progam to support resizing tests Theodore Ts'o
2013-04-01 0:44 ` [PATCH 4/4] tests: add more tests for off-line resizing Theodore Ts'o
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=5153BFA5.9090404@redhat.com \
--to=sandeen@redhat.com \
--cc=john.jolly@gmail.com \
--cc=linux-ext4@vger.kernel.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 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).