public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
* xlog_space_left: head behind tail ?
@ 2012-09-24  4:49 Gregory Machin
  2012-09-24  7:26 ` Dave Chinner
  0 siblings, 1 reply; 3+ messages in thread
From: Gregory Machin @ 2012-09-24  4:49 UTC (permalink / raw)
  To: xfs

Hi.

Since I started using Acronis backup software I have the following in my logs :

Sep 22 18:00:16 nzhmlfpr04 kernel: session_stat: dev=8:1 state=6
blksize=1024 mmapsize=262144
Sep 22 18:00:16 nzhmlfpr04 kernel: session_stat: psize=1024000
pstrt=2048 mshft=0 ioctls=728
Sep 22 18:00:16 nzhmlfpr04 kernel: session_stat: bhpgs=0 bhcnt=0
abhs=307 fbhs=307 dbhs=0
Sep 22 18:00:16 nzhmlfpr04 kernel: session_stat: gpgs=30836 ppgs=30836
emmax=30662 emmin=28746 emcur=0 cached=0
Sep 22 18:00:16 nzhmlfpr04 kernel: session_stat: rblk=9321 cblk=95
rcblk=46 rc2blk=0 mcblk=38 rwcolls=11
Sep 22 18:00:16 nzhmlfpr04 kernel: session_stat: sync=0 async=26 aretr=0
Sep 22 18:00:16 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
Sep 22 18:00:16 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26561024
Sep 22 18:00:16 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26540592
Sep 22 18:00:16 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
Sep 22 18:00:16 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26561024
Sep 22 18:00:16 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26540592
Sep 22 18:00:16 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
Sep 22 18:00:16 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26561024
Sep 22 18:00:16 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26541608
Sep 22 18:00:16 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
Sep 22 18:00:16 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26561024
Sep 22 18:00:16 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26541608
Sep 22 18:00:17 nzhmlfpr04 kernel: XFS (dm-5): xlog_space_left: head behind tail
Sep 22 18:00:17 nzhmlfpr04 kernel:  tail_cycle = 2052, tail_bytes = 3527680
Sep 22 18:00:17 nzhmlfpr04 kernel:  GH   cycle = 2052, GH   bytes = 3510104
Sep 22 18:00:17 nzhmlfpr04 kernel: XFS (dm-5): xlog_space_left: head behind tail
Sep 22 18:00:17 nzhmlfpr04 kernel:  tail_cycle = 2052, tail_bytes = 3527680
Sep 22 18:00:17 nzhmlfpr04 kernel:  GH   cycle = 2052, GH   bytes = 3510104
Sep 22 18:00:24 nzhmlfpr04 kernel: XFS (dm-3): xlog_space_left: head behind tail
Sep 22 18:00:24 nzhmlfpr04 kernel:  tail_cycle = 125, tail_bytes = 438272
Sep 22 18:00:24 nzhmlfpr04 kernel:  GH   cycle = 125, GH   bytes = 416952
Sep 22 18:00:24 nzhmlfpr04 kernel: XFS (dm-3): xlog_space_left: head behind tail
Sep 22 18:00:24 nzhmlfpr04 kernel:  tail_cycle = 125, tail_bytes = 438272
Sep 22 18:00:24 nzhmlfpr04 kernel:  GH   cycle = 125, GH   bytes = 416952
Sep 22 18:00:30 nzhmlfpr04 kernel: XFS (dm-4): xlog_space_left: head behind tail
Sep 22 18:00:30 nzhmlfpr04 kernel:  tail_cycle = 46, tail_bytes = 11395072
Sep 22 18:00:30 nzhmlfpr04 kernel:  GH   cycle = 46, GH   bytes = 11375664
Sep 22 18:00:30 nzhmlfpr04 kernel: XFS (dm-4): xlog_space_left: head behind tail
Sep 22 18:00:30 nzhmlfpr04 kernel:  tail_cycle = 46, tail_bytes = 11395072
Sep 22 18:00:30 nzhmlfpr04 kernel:  GH   cycle = 46, GH   bytes = 11375664
Sep 22 18:00:33 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
Sep 22 18:00:33 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26563072
Sep 22 18:00:33 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26542632
Sep 22 18:00:33 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
Sep 22 18:00:33 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26563072
Sep 22 18:00:33 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26542632
Sep 22 18:00:47 nzhmlfpr04 kernel: XFS (dm-5): xlog_space_left: head behind tail
Sep 22 18:00:47 nzhmlfpr04 kernel:  tail_cycle = 2052, tail_bytes = 3529728
Sep 22 18:00:47 nzhmlfpr04 kernel:  GH   cycle = 2052, GH   bytes = 3511128
Sep 22 18:00:47 nzhmlfpr04 kernel: XFS (dm-5): xlog_space_left: head behind tail
Sep 22 18:00:47 nzhmlfpr04 kernel:  tail_cycle = 2052, tail_bytes = 3529728
Sep 22 18:00:47 nzhmlfpr04 kernel:  GH   cycle = 2052, GH   bytes = 3511128
Sep 22 18:00:54 nzhmlfpr04 kernel: XFS (dm-3): xlog_space_left: head behind tail
Sep 22 18:00:54 nzhmlfpr04 kernel:  tail_cycle = 125, tail_bytes = 439296
Sep 22 18:00:54 nzhmlfpr04 kernel:  GH   cycle = 125, GH   bytes = 417976
Sep 22 18:00:54 nzhmlfpr04 kernel: XFS (dm-3): xlog_space_left: head behind tail
Sep 22 18:00:54 nzhmlfpr04 kernel:  tail_cycle = 125, tail_bytes = 439296
Sep 22 18:00:54 nzhmlfpr04 kernel:  GH   cycle = 125, GH   bytes = 417976
Sep 22 18:01:00 nzhmlfpr04 kernel: XFS (dm-4): xlog_space_left: head behind tail
Sep 22 18:01:00 nzhmlfpr04 kernel:  tail_cycle = 46, tail_bytes = 11396096
Sep 22 18:01:00 nzhmlfpr04 kernel:  GH   cycle = 46, GH   bytes = 11376688
Sep 22 18:01:00 nzhmlfpr04 kernel: XFS (dm-4): xlog_space_left: head behind tail
Sep 22 18:01:00 nzhmlfpr04 kernel:  tail_cycle = 46, tail_bytes = 11396096
Sep 22 18:01:00 nzhmlfpr04 kernel:  GH   cycle = 46, GH   bytes = 11376688
Sep 22 18:01:03 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
Sep 22 18:01:03 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26564096
Sep 22 18:01:03 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26543656
Sep 22 18:01:03 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
Sep 22 18:01:03 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26564096
Sep 22 18:01:03 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26543656
Sep 22 18:01:17 nzhmlfpr04 kernel: XFS (dm-5): xlog_space_left: head behind tail
Sep 22 18:01:17 nzhmlfpr04 kernel:  tail_cycle = 2052, tail_bytes = 3530752
Sep 22 18:01:17 nzhmlfpr04 kernel:  GH   cycle = 2052, GH   bytes = 3512152
Sep 22 18:01:17 nzhmlfpr04 kernel: XFS (dm-5): xlog_space_left: head behind tail
Sep 22 18:01:17 nzhmlfpr04 kernel:  tail_cycle = 2052, tail_bytes = 3530752
Sep 22 18:01:17 nzhmlfpr04 kernel:  GH   cycle = 2052, GH   bytes = 3512152
Sep 22 18:09:41 nzhmlfpr04 kernel: session_stat: dev=fd:2 state=6
blksize=4096 mmapsize=262144
Sep 22 18:09:41 nzhmlfpr04 kernel: session_stat: psize=209707008
pstrt=0 mshft=0 ioctls=170766
Sep 22 18:09:41 nzhmlfpr04 kernel: session_stat: bhpgs=0 bhcnt=0
abhs=85404 fbhs=85404 dbhs=0
Sep 22 18:09:41 nzhmlfpr04 kernel: session_stat: gpgs=31595 ppgs=31595
emmax=30662 emmin=28746 emcur=0 cached=0
Sep 22 18:09:41 nzhmlfpr04 kernel: session_stat: rblk=5460184 cblk=1
rcblk=1 rc2blk=0 mcblk=1 rwcolls=0
Sep 22 18:09:41 nzhmlfpr04 kernel: session_stat: sync=0 async=1 aretr=0
Sep 22 18:10:10 nzhmlfpr04 kernel: session_stat: dev=fd:0 state=6
blksize=4096 mmapsize=262144
Sep 22 18:10:10 nzhmlfpr04 kernel: session_stat: psize=78725120
pstrt=0 mshft=0 ioctls=25526
Sep 22 18:10:10 nzhmlfpr04 kernel: session_stat: bhpgs=0 bhcnt=0
abhs=4658 fbhs=4658 dbhs=0
Sep 22 18:10:10 nzhmlfpr04 kernel: session_stat: gpgs=31622 ppgs=31622
emmax=30662 emmin=28746 emcur=0 cached=0
Sep 22 18:10:10 nzhmlfpr04 kernel: session_stat: rblk=193051 cblk=525
rcblk=525 rc2blk=0 mcblk=246 rwcolls=53
Sep 22 18:10:10 nzhmlfpr04 kernel: session_stat: sync=0 async=525 aretr=0
Sep 22 18:10:10 nzhmlfpr04 kernel: session_unlockdev: No lock for
device (FD00001) in session (ffff880116b6c000)

Then I found these :
Sep 22 20:17:17 nzhmlfpr04 kernel:  tail_cycle = 2052, tail_bytes = 3572736
Sep 22 20:17:17 nzhmlfpr04 kernel:  GH   cycle = 2052, GH   bytes = 3554064
Sep 22 20:17:24 nzhmlfpr04 kernel: XFS (dm-3): xlog_space_left: head behind tail
Sep 22 20:17:24 nzhmlfpr04 kernel:  tail_cycle = 125, tail_bytes = 488448
Sep 22 20:17:24 nzhmlfpr04 kernel:  GH   cycle = 125, GH   bytes = 467056
Sep 22 20:17:24 nzhmlfpr04 kernel: XFS (dm-3): xlog_space_left: head behind tail
Sep 22 20:17:24 nzhmlfpr04 kernel:  tail_cycle = 125, tail_bytes = 488448
Sep 22 20:17:24 nzhmlfpr04 kernel:  GH   cycle = 125, GH   bytes = 467056
Sep 22 20:17:30 nzhmlfpr04 kernel: XFS (dm-4): xlog_space_left: head behind tail
Sep 22 20:17:30 nzhmlfpr04 kernel:  tail_cycle = 46, tail_bytes = 11430912
Sep 22 20:17:30 nzhmlfpr04 kernel:  GH   cycle = 46, GH   bytes = 11411432
Sep 22 20:17:30 nzhmlfpr04 kernel: XFS (dm-4): xlog_space_left: head behind tail
Sep 22 20:17:30 nzhmlfpr04 kernel:  tail_cycle = 46, tail_bytes = 11430912
Sep 22 20:17:30 nzhmlfpr04 kernel:  GH   cycle = 46, GH   bytes = 11411432
Sep 22 20:17:33 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
Sep 22 20:17:33 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26600960
Sep 22 20:17:33 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26580440
Sep 22 20:17:33 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
Sep 22 20:17:33 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26600960
Sep 22 20:17:33 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26580440
Sep 22 20:17:47 nzhmlfpr04 kernel: XFS (dm-5): xlog_space_left: head behind tail
Sep 22 20:17:47 nzhmlfpr04 kernel:  tail_cycle = 2052, tail_bytes = 3573760
Sep 22 20:17:47 nzhmlfpr04 kernel:  GH   cycle = 2052, GH   bytes = 3555088
Sep 22 20:17:47 nzhmlfpr04 kernel: XFS (dm-5): xlog_space_left: head behind tail
Sep 22 20:17:47 nzhmlfpr04 kernel:  tail_cycle = 2052, tail_bytes = 3573760
Sep 22 20:17:47 nzhmlfpr04 kernel:  GH   cycle = 2052, GH   bytes = 3555088
Sep 22 20:17:54 nzhmlfpr04 kernel: XFS (dm-3): xlog_space_left: head behind tail
Sep 22 20:17:54 nzhmlfpr04 kernel:  tail_cycle = 125, tail_bytes = 489472
Sep 22 20:17:54 nzhmlfpr04 kernel:  GH   cycle = 125, GH   bytes = 468080
Sep 22 20:17:54 nzhmlfpr04 kernel: XFS (dm-3): xlog_space_left: head behind tail
Sep 22 20:17:54 nzhmlfpr04 kernel:  tail_cycle = 125, tail_bytes = 489472
Sep 22 20:17:54 nzhmlfpr04 kernel:  GH   cycle = 125, GH   bytes = 468080
Sep 22 20:19:07 nzhmlfpr04 kernel: XFS (snumbd11d): Corruption
detected. Unmount and run xfs_repair
Sep 22 20:19:07 nzhmlfpr04 kernel: XFS (snumbd11d): inode 0x13461d0d
background reclaim flush failed with 117
Sep 22 20:19:07 nzhmlfpr04 kernel: XFS (snumbd11d): Corruption
detected. Unmount and run xfs_repair
Sep 22 20:19:07 nzhmlfpr04 kernel: XFS (snumbd11d): inode 0x13461d0e
background reclaim flush failed with 117
Sep 22 20:19:07 nzhmlfpr04 kernel: XFS (snumbd11d): Corruption
detected. Unmount and run xfs_repair
Sep 22 20:19:07 nzhmlfpr04 kernel: XFS (snumbd11d): inode 0x13461d0f
background reclaim flush failed with 117
Sep 22 20:19:37 nzhmlfpr04 kernel: XFS (snumbd11d): Corruption
detected. Unmount and run xfs_repair
Sep 22 20:19:37 nzhmlfpr04 kernel: XFS (snumbd11d): inode 0x13461d0d
background reclaim flush failed with 117
Sep 22 20:19:37 nzhmlfpr04 kernel: XFS (snumbd11d): Corruption
detected. Unmount and run xfs_repair
Sep 22 20:19:37 nzhmlfpr04 kernel: XFS (snumbd11d): inode 0x13461d0e
background reclaim flush failed with 117
Sep 22 20:19:37 nzhmlfpr04 kernel: XFS (snumbd11d): Corruption
detected. Unmount and run xfs_repair
Sep 22 20:19:37 nzhmlfpr04 kernel: XFS (snumbd11d): inode 0x13461d0f
background reclaim flush failed with 117
Sep 22 20:20:07 nzhmlfpr04 kernel: XFS (snumbd11d): Corruption
detected. Unmount and run xfs_repair
Sep 22 20:20:07 nzhmlfpr04 kernel: XFS (snumbd11d): inode 0x13461d0d
background reclaim flush failed with 117
Sep 22 20:20:07 nzhmlfpr04 kernel: XFS (snumbd11d): Corruption
detected. Unmount and run xfs_repair
Sep 22 20:20:07 nzhmlfpr04 kernel: XFS (snumbd11d): inode 0x13461d0e
background reclaim flush failed with 117
Sep 22 20:20:07 nzhmlfpr04 kernel: XFS (snumbd11d): Corruption
detected. Unmount and run xfs_repair
Sep 22 20:20:07 nzhmlfpr04 kernel: XFS (snumbd11d): inode 0x13461d0f
background reclaim flush failed with 117


What is the cause for the first lot of logs and are they an issue ?
Did what was causing the first lot of logs create the second
"Corruption detected. Unmount and run xfs_repair"

I ran the xfs_repair and this has relosved the "Corruption detected.
Unmount and run xfs_repair" issue

I want to be sure before I start pointing fingures and asking
questions as to why I'm seeing the first lot of logs and what else
could have cause the 2nd ?

Thanks

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: xlog_space_left: head behind tail ?
  2012-09-24  4:49 xlog_space_left: head behind tail ? Gregory Machin
@ 2012-09-24  7:26 ` Dave Chinner
       [not found]   ` <CAJzjPK=cvXZKdxhPeCjNO0QCGM7KRqJH8gy6B=EHH_xC-UkwkQ@mail.gmail.com>
  0 siblings, 1 reply; 3+ messages in thread
From: Dave Chinner @ 2012-09-24  7:26 UTC (permalink / raw)
  To: Gregory Machin; +Cc: xfs

On Mon, Sep 24, 2012 at 04:49:43PM +1200, Gregory Machin wrote:
> Hi.
> 
> Since I started using Acronis backup software I have the following in my logs :

What kernel?

> Sep 22 18:00:16 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
> Sep 22 18:00:16 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26561024
> Sep 22 18:00:16 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26540592

20,432 bytes behind.

...
> Sep 22 18:01:03 nzhmlfpr04 kernel: XFS (dm-2): xlog_space_left: head behind tail
> Sep 22 18:01:03 nzhmlfpr04 kernel:  tail_cycle = 20, tail_bytes = 26564096
> Sep 22 18:01:03 nzhmlfpr04 kernel:  GH   cycle = 20, GH   bytes = 26543656

And that's 20440 bytes behind. So, an 8 byte leak - sounds rather
familiar:

$ gl -n 1 3948659
commit 3948659e30808fbaa7673bbe89de2ae9769e20a7
Author: Dave Chinner <dchinner@redhat.com>
Date:   Thu Mar 22 05:15:11 2012 +0000

    xfs: Account log unmount transaction correctly
    
    There have been a few reports of this warning appearing recently:
    
    XFS (dm-4): xlog_space_left: head behind tail
     tail_cycle = 129, tail_bytes = 20163072
     GH   cycle = 129, GH   bytes = 20162880
    
    The common cause appears to be lots of freeze and unfreeze cycles,
    and the output from the warnings indicates that we are leaking
    around 8 bytes of log space per freeze/unfreeze cycle.
    
    When we freeze the filesystem, we write an unmount record and that
    uses xlog_write directly - a special type of transaction,
    effectively. What it doesn't do, however, is correctly account for
    the log space it uses. The unmount record writes an 8 byte structure
    with a special magic number into the log, and the space this
    consumes is not accounted for in the log ticket tracking the
    operation. Hence we leak 8 bytes every unmount record that is
    written.
    
    Signed-off-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Ben Myers <bpm@sgi.com>
$ git describe --contains 3948659
v3.4-rc1~55^2~3

So, fixed in 3.4.

FWIW, this commit is in the series I proposed recently for back
porting to 3.0.x stable kernel.

....

> Sep 22 20:17:54 nzhmlfpr04 kernel: XFS (dm-3): xlog_space_left: head behind tail
                                          ^^^^
> Sep 22 20:17:54 nzhmlfpr04 kernel:  tail_cycle = 125, tail_bytes = 489472
> Sep 22 20:17:54 nzhmlfpr04 kernel:  GH   cycle = 125, GH   bytes = 468080
> Sep 22 20:19:07 nzhmlfpr04 kernel: XFS (snumbd11d): Corruption
                                          ^^^^^^^^^
> detected. Unmount and run xfs_repair

Note the different device names the errors are for? So the log space
warnings are from different filesystems to the one that corruption
has been found on. IOWs, unrelated.

> I want to be sure before I start pointing fingures and asking
> questions as to why I'm seeing the first lot of logs

Acronis is freezing/thawing the filesystem to get a consistent
backup image, hence triggering the problem.

> and what else
> could have cause the 2nd ?

Don't know. There's no stack trace in the error message, so I don't
even know where it came from. have you modified the xfs_error_level
sysctl to turn off verbose reporting?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: xlog_space_left: head behind tail ?
       [not found]   ` <CAJzjPK=cvXZKdxhPeCjNO0QCGM7KRqJH8gy6B=EHH_xC-UkwkQ@mail.gmail.com>
@ 2012-09-24 10:50     ` Dave Chinner
  0 siblings, 0 replies; 3+ messages in thread
From: Dave Chinner @ 2012-09-24 10:50 UTC (permalink / raw)
  To: Gregory Machin; +Cc: xfs

[ please leave the mailing list CC on responses. thanks. ]

[Fixed up the top posting mess, too]

On Mon, Sep 24, 2012 at 09:29:04PM +1200, Gregory Machin wrote:
> On Mon, Sep 24, 2012 at 7:26 PM, Dave Chinner <david@fromorbit.com> wrote:
> > On Mon, Sep 24, 2012 at 04:49:43PM +1200, Gregory Machin wrote:
> >> Hi.
> >>
> >> Since I started using Acronis backup software I have the following in my logs :
> >
> > What kernel?
>
> The Kernel : Linux nzhmlfpr04 2.6.32-279.5.2.el6.x86_64 #1 SMP Fri Aug
> 24 01:07:11 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> OS CentOS : 6.3

So, it doesn't have the fix. You'll have to upgrade to 3.4 or
backport the patch yourself.

> >> Sep 22 20:17:54 nzhmlfpr04 kernel: XFS (dm-3): xlog_space_left: head behind tail
> >                                           ^^^^
> >> Sep 22 20:17:54 nzhmlfpr04 kernel:  tail_cycle = 125, tail_bytes = 489472
> >> Sep 22 20:17:54 nzhmlfpr04 kernel:  GH   cycle = 125, GH   bytes = 468080
> >> Sep 22 20:19:07 nzhmlfpr04 kernel: XFS (snumbd11d): Corruption
> >                                           ^^^^^^^^^
> >> detected. Unmount and run xfs_repair
> >
> > Note the different device names the errors are for? So the log space
> > warnings are from different filesystems to the one that corruption
> > has been found on. IOWs, unrelated.
>
> There are 4 xfs filesystems mounted on that machine.

According to the logs, there are at least 5: dm-{2,3,4,5} and
snumbd11d.

> >> and what else
> >> could have cause the 2nd ?
> >
> > Don't know. There's no stack trace in the error message, so I don't
> > even know where it came from. have you modified the xfs_error_level
> > sysctl to turn off verbose reporting?
>
> sysctl.conf is default for CentOS.

So there's an error that isn't reporting a stack by default. That
means it is probably a directory read that is triggering it -
knowing what errors xfs_repair reported would help narrow it down.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-09-24 10:49 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-09-24  4:49 xlog_space_left: head behind tail ? Gregory Machin
2012-09-24  7:26 ` Dave Chinner
     [not found]   ` <CAJzjPK=cvXZKdxhPeCjNO0QCGM7KRqJH8gy6B=EHH_xC-UkwkQ@mail.gmail.com>
2012-09-24 10:50     ` Dave Chinner

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox