lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpYoaWEYTQBE_Lb7dKGa2P=AT8F77=0E-6HWEDAeRaWUTzueg@mail.gmail.com>
Date:	Sat, 18 Apr 2015 13:46:20 +0100
From:	Daniel Johnson <dan.u.johns@...il.com>
To:	linux-ext4@...r.kernel.org
Subject: Using latest e2fsprogs on various offline VM ext filesystems

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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ