From: Daniel Johnson <dan.u.johns@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Using latest e2fsprogs on various offline VM ext filesystems
Date: Sat, 18 Apr 2015 13:46:20 +0100 [thread overview]
Message-ID: <CANpYoaWEYTQBE_Lb7dKGa2P=AT8F77=0E-6HWEDAeRaWUTzueg@mail.gmail.com> (raw)
Apologies if this "user" question has been asked before.
Tomorrow I will be stopping a couple of dozen kvm virtual machines
running various Linux distros and running a forced e2fsck on all of
their ext filesystems. The distros are a mix of various flavours of
Ubuntu, Debian and Centos, so will include some fs created with older
kernels and E2fsprogs.
The host is 64-bit Centos 6 running vanilla kernel 3.14.39. I figured
I'll build the latest E2fsprogs 1.42.12 for this rather than using the
Centos 6 e2fsprogs-1.41.12-21.el6.x86_64.
My question is; should it be safe in theory to use the latest
E2fsprogs on a mix of ext filesystems in this way? I would have
thought so but don't want to rely on any assumptions :-)
I'll be setting up device maps on the host server to get to the
filesystems on each VMs virtual disk, and doing read only checks. But
if anything needs a repair then I could potentially have a fs modified
on newer kernel & userspace that then has to boot inside a VM with a
distro with much older kernel and userspace such as Centos 5, which is
what I'm concerned about.
Thanks,
Dan
next reply other threads:[~2015-04-18 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-18 12:46 Daniel Johnson [this message]
2015-04-18 15:12 ` Using latest e2fsprogs on various offline VM ext filesystems Andreas Dilger
2015-04-18 20:30 ` Daniel Johnson
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='CANpYoaWEYTQBE_Lb7dKGa2P=AT8F77=0E-6HWEDAeRaWUTzueg@mail.gmail.com' \
--to=dan.u.johns@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).