| To: | Jesse Stroik <jstroik@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Seg fault during xfs repair (segmentation fault / segv) |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Wed, 01 Jul 2009 15:52:25 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <4A4BCC44.7050302@xxxxxxxxxxxxx> |
| References: | <4A4A596D.8030800@xxxxxxxxxxxxx> <4A4A5C4E.7030605@xxxxxxxxxxx> <4A4A7D44.7040009@xxxxxxxxxxxxx> <4A4BBECC.8000308@xxxxxxxxxxx> <4A4BC83A.3080401@xxxxxxxxxxx> <4A4BCC44.7050302@xxxxxxxxxxxxx> |
| User-agent: | Thunderbird 2.0.0.22 (Macintosh/20090605) |
Jesse Stroik wrote: > Eric, > > Thanks for addressing the issue with xfs_repair. > > >> that's one crunchy filesystem you've got there; what happened to it? > > > It's not entirely clear -- the JBOD and SAS controller seem to have > gotten into inconsistent states and I was observing a few SCSI errors > for those particular LUNs. While the system was exhibiting the SCSI > errors, the user of this file system (and a few others like it on the > host) noticed file corruption when reading/writing certain files, then > spontaneous corruption after making copies of the files. > > I'll take a look at the new xfs_check and see what happens. > > Best, > Jesse > Turns out that it runs to completion, but another run still finds corruption. And a debug build trips asserts, so I guess there are still issues. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Seg fault during xfs repair (segmentation fault / segv), Jesse Stroik |
|---|---|
| Next by Date: | Re: [PATCH] xfs_repair: fix verify_ag_bno() overflow, Eric Sandeen |
| Previous by Thread: | Re: Seg fault during xfs repair (segmentation fault / segv), Jesse Stroik |
| Next by Thread: | [PATCH] xfs_repair: fix verify_ag_bno() overflow, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |