From: Jakob Haufe <sur5r@sur5r.net>
To: linux-ext4@vger.kernel.org
Subject: Re: online resize of ext4 hung (3.2.51 / 1.42.5)
Date: Mon, 28 Oct 2013 15:39:25 +0100 [thread overview]
Message-ID: <20131028153925.0aa4f31c@samsa> (raw)
In-Reply-To: <20131027060812.GB12361@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
On Sun, 27 Oct 2013 02:08:12 -0400
Theodore Ts'o <tytso@mit.edu> wrote:
> (Sorry for the delay in responding, a number of us have been attending
> a conference in Edinburgh, and I'm currently on vacation in Dublin.)
No problem. I'm really happy about all the responses I got.
> In any case, I think it should be safe for you to reboot your file
> system, and after an fsck -f, I think your file system should be OK.
I did so. For the sake of completeness I've put the log here:
http://permalink.sur5r.net/1/linux-3.2.51-resize2fs-1.42.5-hung-fsck.log
I decided to recreate the filesystem to be on the safe side.
> P.S. To ext4 developers, please note that the kernel involved,
> v3.2.52 does _not_ have Jan Kara's reserved handles changes, which
> were added in commit 8f7d89f36829. I at first thought it might have
> been related to changes involving how jbd2_journal_lock_updates()
> waits for j_reserved_credits to go to zero, but that was a blind
> alley.
In case this wasn't just a typo: The box is running 3.2.51 but I guess this
doesn't make a difference regarding this paragraph.
Cheers,
Jakob
--
ceterum censeo microsoftem esse delendam.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-10-28 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 20:06 online resize of ext4 hung (3.2.51 / 1.42.5) Jakob Haufe
2013-10-25 23:57 ` Theodore Ts'o
2013-10-26 20:51 ` Jakob Haufe
2013-10-27 6:08 ` Theodore Ts'o
2013-10-28 14:39 ` Jakob Haufe [this message]
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=20131028153925.0aa4f31c@samsa \
--to=sur5r@sur5r.net \
--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).