Re: silent corruption after kernel panic?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



mån 2011-09-19 klockan 10:27 -0400 skrev Christoph Hellwig:
> On Mon, Sep 19, 2011 at 02:28:23PM +0200, Assarsson, Emil wrote:
> > Hi,
> > 
> > We are running a 20TB XFS filesystem on top of LVM2 and SAN storage (HP
> > Open-V) with multipathd. Ubuntu Lucid. The disk write cache is enabled
> > and we use mount options rw.
> 
> 
> > Sep 16 06:40:34 seldlnx034 kernel: [54607.977261] XFS internal error
> > XFS_WANT_CORRUPTED_RETURN at line 381 of
> > file /build/buildd/linux-2.6.32/fs/xfs/xfs_alloc.c.  Caller
> > 0xffffffffa01eed36
> > Sep 16 06:40:34 seldlnx034 kernel: [54607.996676]  [<ffffffffa0215383>]
> > xfs_error_report+0x43/0x50 [xfs]
> > Sep 16 06:40:34 seldlnx034 kernel: [54607.996689]
> 
> This (corrupted allocation btrees) is a typical indication of missing
> cache flushes.
> 
> Given that before ~2.6.35 LVM/device mapper was not able to pass through
> cache flush requests that is your most likely culprit.  A repair will
> rebuild the freespace btrees, and make sure to keep the write caches
> down the whole stack disabled.

Thanks for you help Christoph. I guess you are right. Some of our system
had write cache enabled and used Device Mapper. We have disabled the
cache.

We got some new, possibly related, problems and was forced to clear the
log. We decided to move the data to a fresh file system. We will use
xfs_dump/restore.

--
Emil Assarsson
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs



[Index of Archives]     [Linux XFS Devel]     [Linux Filesystem Development]     [Filesystem Testing]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux