[Lustre-discuss] e2fsck claims OST is clean, then dirty

[Andreas Dilger]

On 2010-01-21, at 09:42, Erik Froese wrote:
> =========
> [root at oss-0-0 ~]# dumpe2fs -h /dev/dsk/ost24 | grep state
> dumpe2fs 1.41.6.sun1 (30-May-2009)
> Filesystem state:         clean
> =========

The "clean" state is always true for ext3/ext4/ldiskfs filesystems,  
due to the journal.

> =========
> [root at oss-0-0 ~]# e2fsck -n /dev/dsk/ost24  | tee /state/partition1/ 
> e2fsck-n_ost24_`date '+%m.%d.%y-%H:%M:%S'`.log
> e2fsck 1.41.6.sun1 (30-May-2009)
> device /dev/sdy mounted by lustre per /proc/fs/lustre/obdfilter/ 
> scratch-OST000e/mntdev
> Warning!  /dev/dsk/ost24 is mounted.
> Warning: skipping journal recovery because doing a read-only  
> filesystem check.
> scratch-OSTffff: clean, 3219531/183009280 files, 60844652/732023488  
> blocks
> =========
>
> I ran that again and it produced a ton of errors. Could it be  
> because the OST is active? (Log attached)
> Then I ran it again and it e2fsck reported that the OST was clean.

Checking a mounted filesystem is always at risk of producing  
inconsistent results.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.