| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: XFS internal error |
| From: | Andreas Kotes <count@xxxxxxxxxxx> |
| Date: | Thu, 13 Mar 2008 08:14:45 +0100 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20080313000121.GU155407@sgi.com> |
| References: | <470831E6.4030704@fastmail.co.uk> <20071008001452.GX995458@sgi.com> <20080310122216.GG14256@slop.flatline.de> <20080310223018.GA155407@sgi.com> <20080310225927.GP14256@slop.flatline.de> <20080310234539.GC155407@sgi.com> <20080311134746.GQ14256@slop.flatline.de> <20080312175050.GD14256@slop.flatline.de> <20080313000121.GU155407@sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.13 (2006-08-11) |
Hallo Dave, * David Chinner <dgc@xxxxxxx> [20080313 01:01]: > On Wed, Mar 12, 2008 at 06:50:50PM +0100, Andreas Kotes wrote: > > * Andreas Kotes <count-linux@xxxxxxxxxxx> [20080311 14:47]: > > > I basically build a PXE image which does an xfs_repair -L /dev/sda2 from > > > initrd - and the problem persists. Sigh. Exactly no change. > > Do you do this on every boot? no, I did this on a6b and a7b so far, where the problems I mentioned occur, and only after I saw these in-memory problems. in general, XFS proves to be realiable for us. would you recommend running an xfs_check before running an xfs_repair in case of problems? Br, Andreas -- flatline IT services - Andreas Kotes - Tailored solutions for your IT needs |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE 977766 - Update mkfs manpage for new defaults:, Niv Sardi-Altivanik |
|---|---|
| Next by Date: | Re: XFS internal error, Andreas Kotes |
| Previous by Thread: | Re: XFS internal error, David Chinner |
| Next by Thread: | Re: XFS internal error, Andreas Kotes |
| Indexes: | [Date] [Thread] [Top] [All Lists] |