Hmmmm... I think it might have found a fix. It looks like someone
else had the problem and opened a bug report [Bug 195]. I will
have to check it out.
-Scott
----------------------------------------------------------------
Scott Jepson, Managing Partner Email: scott@xxxxxxxx
Creative Network Services, LLC http://www.cnes.com
(310)470-6140
----------------------------------------------------------------
On Mon, 17 Mar 2003, Scott Jepson wrote:
> Date: Mon, 17 Mar 2003 16:01:46 -0800
> From: Scott Jepson <scott@xxxxxxxx>
> To: linux-xfs@xxxxxxxxxxx
> Subject: Re: xfs_fsr Seg faults
>
> Forgot: I'm running 2.4.20 with linux-2.4.20-xfs-2003-02-23.patch
> and the latest cmds from the CVS tree.
>
> -Scott
>
> ----------------------------------------------------------------
> Scott Jepson, Managing Partner Email: scott@xxxxxxxx
> Creative Network Services, LLC http://www.cnes.com
> (310)470-6140
> ----------------------------------------------------------------
>
> On Mon, 17 Mar 2003, Scott Jepson wrote:
>
> > Date: Mon, 17 Mar 2003 15:33:25 -0800
> > From: Scott Jepson <scott@xxxxxxxx>
> > To: linux-xfs@xxxxxxxxxxx
> > Subject: xfs_fsr Seg faults
> >
> > Hi,
> > I ran xfs_fsr when I had about 70 gigs of files in a 1 TB file
> > system and all was fine. Since then we have added another 100 gigs of
> > files and xfs_fsr Seg faults. Here's what i see in the logs:
> >
> > $ xfs_fsr /mnt/x3
> > /mnt/x3 start inode=0
> > Segmentation fault
> >
> > Mar 17 15:27:55 dragon kernel: <1>Unable to handle kernel paging request
> > at virtual address 654b0911
> > Mar 17 15:27:55 dragon kernel: printing eip:
> > Mar 17 15:27:55 dragon kernel: c01ef8a1
> > Mar 17 15:27:55 dragon kernel: *pde = 00000000
> > Mar 17 15:27:55 dragon kernel: Oops: 0000
> > Mar 17 15:27:55 dragon kernel:
> > Mar 17 15:27:55 dragon kernel: CPU: 0
> > Mar 17 15:27:55 dragon kernel: EIP: 0010:[map_blocks+129/288] Not
> > tainted
> > Mar 17 15:27:55 dragon kernel: EIP: 0010:[<c01ef8a1>] Not tainted
> > Mar 17 15:27:55 dragon kernel: EFLAGS: 00010283
> > Mar 17 15:27:55 dragon kernel: eax: 654b0909 ebx: 00020002 ecx:
> > f5859d84 edx: f66bb2e0
> > Mar 17 15:27:55 dragon kernel: esi: 00000000 edi: 00000000 ebp:
> > 00000000 esp: f5859d7c
> > Mar 17 15:27:55 dragon kernel: ds: 0018 es: 0018 ss: 0018
> > Mar 17 15:27:55 dragon kernel: Process xfs_fsr (pid: 709,
> > stackpage=f5859000)
> > Mar 17 15:27:55 dragon kernel: Stack: f5859d84 f66bb2e0 00000001 f66bb300
> > 00000000 00000000 0001b000 c01f0e78
> > Mar 17 15:27:55 dragon kernel: f66bb300 00000000 00000000 0001b000
> > f5859df8 00020002 01080002 00020002
> > Mar 17 15:27:55 dragon kernel: 0804f000 f66bb2e0 f7127f80 00000000
> > 00000000 0001b000 0001b000 00000000
> > Mar 17 15:27:55 dragon kernel: Call Trace: [linvfs_direct_IO+840/890]
> > [map_user_kiobuf+180/256] [generic_file_direct_IO+423/544]
> > [generic_file_write_nolock+1744/1904] [xfs_write+1012/1696]
> > [xfs_read+411/464] [linvfs_wri
> > te+177/240] [sys_write+150/272] [sys_ioctl+647/657] [system_call+51/56]
> > Mar 17 15:27:55 dragon kernel: Call Trace: [<c01f0e78>] [<c0126064>]
> > [<c012a657>] [<c012c690>] [<c01f6314>] [<c01f5b2b>] [<c01f10a1>]
> > [<c01382d6>] [<c0146d07>] [<c01070c3>]
> > Mar 17 15:27:55 dragon kernel: Code: 8b 50 08 51 8b 74 24 34 56 53 8b 4c
> > 24 38 51 55 57 50 ff 52
> >
> > Any ideas to the problem?
> >
> > Thanks,
> >
> > -Scott
> >
> >
> >
> >
> > ----------------------------------------------------------------
> > Scott Jepson, Managing Partner Email: scott@xxxxxxxx
> > Creative Network Services, LLC http://www.cnes.com
> > (310)470-6140
> > ----------------------------------------------------------------
> >
> >
> >
>
>
>
|