Hi all,
I am trying to perform a file-system check on a mounted lustre file-system.
The e2fsck fails with the following message:
> e2fsck -n -v --mdsdb /tmp/mdsdb /dev/msavg/lv001
e2fsck 1.41.10.sun2 (24-Feb-2010)
device /dev/mapper/msavg-lv001 mounted by lustre per
/proc/fs/lustre/mds/lustrefs-MDT0000/mntdev
Warning! /dev/msavg/lv001 is mounted.
e2fsck: MMP: device currently active while trying to open /dev/msavg/lv001
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 32744 <device>
I tried setting -b argument but the message persists.
Do you have any suggestions on how to proceed.
Best regards
Christos
--
Christos Theodosiou
Scientific Computational Center
Aristotle University
54 124 Thessaloniki, Greece
Tel: +30 2310 99 8988
Fax: +30 2310 99 4309
http://www.grid.auth.gr
you?d better unmount the clients and ost/mdt first, then fsck them. On Wed, Apr 13, 2011 at 4:29 PM, Christos Theodosiou <ctheodos at grid.auth.gr> wrote:> Hi all, > > I am trying to perform a file-system check on a mounted lustre file-system. > > The e2fsck fails with the following message: > > ?> e2fsck -n -v --mdsdb /tmp/mdsdb /dev/msavg/lv001 > e2fsck 1.41.10.sun2 (24-Feb-2010) > device /dev/mapper/msavg-lv001 mounted by lustre per > /proc/fs/lustre/mds/lustrefs-MDT0000/mntdev > Warning! ?/dev/msavg/lv001 is mounted. > e2fsck: MMP: device currently active while trying to open /dev/msavg/lv001 > > The superblock could not be read or does not describe a correct ext2 > filesystem. ?If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > ? ? e2fsck -b 32744 <device> > > I tried setting -b argument but the message persists. > > Do you have any suggestions on how to proceed. > > Best regards > Christos > > -- > Christos Theodosiou > Scientific Computational Center > Aristotle University > 54 124 Thessaloniki, Greece > Tel: +30 2310 99 8988 > Fax: +30 2310 99 4309 > http://www.grid.auth.gr > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss >
Hi Christos, As far as I remember the mmp implementation in the default Lustre e2fsprog has a bug where you can not access filesystem in readonly mode as long as the filesystem is mounted. I downloaded a newer version of the e2fsprog tools which doesn''t have that fault and I have been successfully using this version for 6 months now. e2fsprogs-1.41.12.2.ora1-0redhat.x86_64 e2fsprogs-devel-1.41.12.2.ora1-0redhat.x86_64 So if you upgrade your e2fsprogs to newer version you should not have a problem to run fsck with -n Other option you have is to temporarily disable the MMP protection but I am not sure if you can do that while device is mounted. Best regards, Wojciech On 13 April 2011 09:29, Christos Theodosiou <ctheodos at grid.auth.gr> wrote:> Hi all, > > I am trying to perform a file-system check on a mounted lustre file-system. > > The e2fsck fails with the following message: > > > e2fsck -n -v --mdsdb /tmp/mdsdb /dev/msavg/lv001 > e2fsck 1.41.10.sun2 (24-Feb-2010) > device /dev/mapper/msavg-lv001 mounted by lustre per > /proc/fs/lustre/mds/lustrefs-MDT0000/mntdev > Warning! /dev/msavg/lv001 is mounted. > e2fsck: MMP: device currently active while trying to open /dev/msavg/lv001 > > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 32744 <device> > > I tried setting -b argument but the message persists. > > Do you have any suggestions on how to proceed. > > Best regards > Christos > > -- > Christos Theodosiou > Scientific Computational Center > Aristotle University > 54 124 Thessaloniki, Greece > Tel: +30 2310 99 8988 > Fax: +30 2310 99 4309 > http://www.grid.auth.gr > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > http://lists.lustre.org/mailman/listinfo/lustre-discuss >-- Wojciech Turek Senior System Architect High Performance Computing Service University of Cambridge Email: wjt27 at cam.ac.uk Tel: (+)44 1223 763517 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110413/eed356df/attachment.html
Hi Wojciech, upgrading e2fsprog worked fine. Thank you Christos On 04/13/2011 02:29 PM, Wojciech Turek wrote:> Hi Christos, > > As far as I remember the mmp implementation in the default Lustre > e2fsprog has a bug where you can not access filesystem in readonly > mode as long as the filesystem is mounted. I downloaded a newer > version of the e2fsprog tools which doesn''t have that fault and I have > been successfully using this version for 6 months now. > > e2fsprogs-1.41.12.2.ora1-0redhat.x86_64 > e2fsprogs-devel-1.41.12.2.ora1-0redhat.x86_64 > > So if you upgrade your e2fsprogs to newer version you should not have > a problem to run fsck with -n > > Other option you have is to temporarily disable the MMP protection but > I am not sure if you can do that while device is mounted. > > Best regards, > > Wojciech > > > On 13 April 2011 09:29, Christos Theodosiou <ctheodos at grid.auth.gr > <mailto:ctheodos at grid.auth.gr>> wrote: > > Hi all, > > I am trying to perform a file-system check on a mounted lustre > file-system. > > The e2fsck fails with the following message: > > > e2fsck -n -v --mdsdb /tmp/mdsdb /dev/msavg/lv001 > e2fsck 1.41.10.sun2 (24-Feb-2010) > device /dev/mapper/msavg-lv001 mounted by lustre per > /proc/fs/lustre/mds/lustrefs-MDT0000/mntdev > Warning! /dev/msavg/lv001 is mounted. > e2fsck: MMP: device currently active while trying to open > /dev/msavg/lv001 > > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the > superblock > is corrupt, and you might try running e2fsck with an alternate > superblock: > e2fsck -b 32744 <device> > > I tried setting -b argument but the message persists. > > Do you have any suggestions on how to proceed. > > Best regards > Christos > > -- > Christos Theodosiou > Scientific Computational Center > Aristotle University > 54 124 Thessaloniki, Greece > Tel: +30 2310 99 8988 > Fax: +30 2310 99 4309 > http://www.grid.auth.gr > > _______________________________________________ > Lustre-discuss mailing list > Lustre-discuss at lists.lustre.org > <mailto:Lustre-discuss at lists.lustre.org> > http://lists.lustre.org/mailman/listinfo/lustre-discuss > > > > > -- > Wojciech Turek > > Senior System Architect > > High Performance Computing Service > University of Cambridge > Email: wjt27 at cam.ac.uk <mailto:wjt27 at cam.ac.uk> > Tel: (+)44 1223 763517-- Christos Theodosiou Scientific Computational Center Aristotle University 54 124 Thessaloniki, Greece Tel: +30 2310 99 8988 Fax: +30 2310 99 4309 http://www.grid.auth.gr -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110413/e07ce616/attachment.html