From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: Re: 64bit + resize2fs... this is Not Good.
Date: 14 Nov 2012 02:20:21 -0500 [thread overview]
Message-ID: <20121114072021.28351.qmail@science.horizon.com> (raw)
In-Reply-To: <20121114054347.GA20380@thunk.org>
> So the first question is figuring out why the on-line resizing didn't
> work for you, since that is what I've spent most of my time trying to
> fix up. The secondary question then is trying to figure out whappened
> with the off-line resize, and to fix that bug in e2fsprogs.
If you don't mind, *my* primary question is "what can I salvage from this
rubble?", since I didn't happen to have 8 TB of backup space available
to me when I did the resize, and there's soem stuff on the FS I'd
rather not lose...
So my big question is "where the F did inodes 129 through 2048
get copied to?", since the root directory contains a lot of inodes
in that range, and every one I can recover saves a lot of
pawing through lost+found later...
In hindsght, I wish to hell I had turned on -d 14 and logged the
results...
If you happen to want to rerun your test with -d8 and tell me what
happened there, I'd definitely appreciate it.
next prev parent reply other threads:[~2012-11-14 7:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 3:51 64bit + resize2fs... this is Not Good George Spelvin
2012-11-14 5:43 ` Theodore Ts'o
2012-11-14 6:42 ` George Spelvin
2012-11-14 7:12 ` George Spelvin
2012-11-14 7:20 ` George Spelvin [this message]
2012-11-14 20:39 ` Theodore Ts'o
2012-11-14 21:04 ` Theodore Ts'o
2012-11-14 23:26 ` George Spelvin
2012-11-14 23:38 ` Theodore Ts'o
2012-11-15 3:43 ` George Spelvin
2012-11-14 6:27 ` George Spelvin
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=20121114072021.28351.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).