Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Aug 2009 15:15:44 -0500
From:      "Hearn, Trevor" <trevor.hearn@Vanderbilt.Edu>
To:        John Baldwin <jhb@freebsd.org>
Cc:        "freebsd-fs@freebsd.org" <freebsd-fs@freebsd.org>
Subject:   RE: UFS Filesystem issues, and the loss of my hair...
Message-ID:  <8E9591D8BCB72D4C8DE0884D9A2932DC35BD34CC@ITS-HCWNEM03.ds.Vanderbilt.edu>
In-Reply-To: <200908101605.12332.jhb@freebsd.org>
References:  <8E9591D8BCB72D4C8DE0884D9A2932DC35BD34C3@ITS-HCWNEM03.ds.Vanderbilt.edu> <200908070829.54571.jhb@freebsd.org> <8E9591D8BCB72D4C8DE0884D9A2932DC35BD34CA@ITS-HCWNEM03.ds.Vanderbilt.edu>, <200908101605.12332.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Here is the chunk that I grabbed from the screen to save as a memento. :)

Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-641956995000=
8350720, length=3D16384)]error =3D 5
Aug 10 10:53:43 XXXX last message repeated 20 times
Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-641956995000=
8350720, length=3D1638d)]error =3D 5
Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-641956995000=
8350720, length=3D16384)]error =3D 5
Aug 10 10:53:43 XXXX last message repeated 18 times
Aug 10 10:53:43 XXXX kernel: g_vfs_done()-da1p7[READ(offset=3D
Aug 10 10:53:43 XXXX kernel: -6419569950008350720, length=3D16384)]error =
=3D 5
Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-641956995000=
8350720, length=3D16384)]error =3D 5
Aug 10 10:53:43 XXXX last message repeated 19 times
Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-641956995000=
8350720, l=3Dngth=3D16384)]error 1 5
Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-641956995000=
8350720, length=3D16384)]error =3D 5
Aug 10 10:53:43 XXXX last message repeated 6 times
Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-641956995000=
8350720, length=3D16384o]error =3D 5
Aug 10 10:53:43 XXXX kernel:
Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-641956995000=
8350720, length=3D16384)]error =3D 5
Aug 10 10:53:43 XXXX last message repeated 22 times
Aug 10 10:53:44 XXXX kernel: READ(offset=3D-6419569950008350720, length=3D1=
6384)]error =3D 5
Aug 10 10:53:44 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-641956995000=
8350720, length=3D16384)]error =3D 5
Aug 10 10:53:44 XXXX last message repeated 849 times

As you can see, it's a little disjointed. I would assume that the screwed u=
p length information is from the speed at which it was coming out, and poss=
ibly another message got throw in at the same time?=20

-Trevor
________________________________________
From: John Baldwin [jhb@freebsd.org]
Sent: Monday, August 10, 2009 3:05 PM
To: Hearn, Trevor
Cc: freebsd-fs@freebsd.org
Subject: Re: UFS Filesystem issues, and the loss of my hair...

On Monday 10 August 2009 3:31:23 pm Hearn, Trevor wrote:
> To the FreeBSD-FS group at large...
>
> Well, I've spent alot of time looking this one over... I setup a share on=
 a webserver to put up redacted images of the errors I am getting. They are=
 here:
>
> http://www.trevorhearn.com/Array/IMG_0056.jpg
> http://www.trevorhearn.com/Array/IMG_0061.jpg
> http://www.trevorhearn.com/Array/IMG_0063.jpg
> http://www.trevorhearn.com/Array/IMG_0065.jpg
> http://www.trevorhearn.com/Array/IMG_0067.jpg
> http://www.trevorhearn.com/Array/IMG_0069.jpg
>
> So, while I am in a meeting about the array, oddly, I have this come roll=
ing across the screen of the terminal session I am in...
>
> Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-6419569950=
008350720, length=3D16384)]error =3D 5
> Aug 10 10:53:43 XXXX last message repeated 20 times
> Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-6419569950=
008350720, length=3D1638d)]error =3D 5
> Aug 10 10:53:43 XXXX kernel: g_vfs_done():da1p7[READ(offset=3D-6419569950=
008350720, length=3D16384)]error =3D 5
> Aug 10 10:53:43 XXXX last message repeated 18 times

Is the '1638d' above a typo in the cut and paste or does it actually have a
'd' instead of a '4' in the log?  '4' is 0x34 and 'd' is 0x64 so that could
be indicative of a two-bit memory error perhaps?

--
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8E9591D8BCB72D4C8DE0884D9A2932DC35BD34CC>