From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@kernel.org
Subject: [Bug 194567] ext4 no longer mounts
Date: Wed, 15 Feb 2017 11:30:50 +0000 [thread overview]
Message-ID: <bug-194567-13602-sN3Laoo7O8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-194567-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=194567
--- Comment #4 from bugzilla.kernel.org@plan9.de ---
First, I'm impressed how quickly this was handled. I am in no pressing need of
a fix (4.4.47 works just as well) and would like to avoid compiling a kernel
just for this fix. Hope this is ok and the issue is "obvious" enough to fix
without it, so from my side, all is well and I can check once this hits a
release kernel.
As for resizing, my lvm history doesn't go back that far, and I don't
specifically remember having it resized, but since the fs has moved through at
least three different disks and contains a slowly growing database, it would be
a prime target for resizing - I certainly do have a habit of resizing
filesystems in general.
On the other hand, wouldn't -O ^resize_inode preclude online resizing? No need
to answer that, you certainly know best. If, however, online resizing wouldn't
work I probably would have played ayround with tune2fs andf/or offline resizing
to make it work.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-02-15 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 20:55 [Bug 194567] New: ext4 no longer mounts bugzilla-daemon
2017-02-13 4:00 ` [Bug 194567] " bugzilla-daemon
2017-02-13 14:59 ` bugzilla-daemon
2017-02-15 6:29 ` bugzilla-daemon
2017-02-15 11:30 ` bugzilla-daemon [this message]
2017-02-15 23:46 ` bugzilla-daemon
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=bug-194567-13602-sN3Laoo7O8@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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