| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: xfs_repair couldn't verify primary superblock |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Thu, 21 Apr 2016 14:34:08 -0400 |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <7ce740a1888c4bb28ce3c30fcedbe703@xxxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <d738a94784a0426e97752f92f38325a0@xxxxxxxxxxxxxxxxxxxxxxxxx> <5717E2EF.1080902@xxxxxxxxxxx> <7ce740a1888c4bb28ce3c30fcedbe703@xxxxxxxxxxxxxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 |
On 4/21/16 10:42 AM, StÃphane Larose wrote: > Hi Eric, > > Nothing more interesting. From the log: > > 2016-04-04T14:48:48.735738-04:00 manitou kernel: [271211.548878] XFS (dm-24): > Mounting V4 Filesystem > 2016-04-04T14:48:48.882738-04:00 manitou kernel: [271211.694242] XFS (dm-24): > Ending clean mount > > Then no more logs about dm-24. > > Also no errors from the underlying storage (verified in SANtricity) > which is an IS5000. The filesystem was new, the first mount was on > 2016-04-04. > > manitou:~ # blkid /dev/dm-24 > /dev/dm-24: UUID="1da22ae2-a572-4db7-b177-b90021a20863" TYPE="xfs" > > Thank you for your help, Any chance that some other host is accessing the same LUN on the SAN? This really looks like something external corrupted the filesystem by writing over it... -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | ÐÐÑÑÐÐÐÐ 275-ÐÐ Ð 159-ÐÐ, ÐÐÐÐÐÐÐÐÑ "Ð ÐÐÑÑÐÐÑÑÑÐÐÐÐÐÐ ÐÐÐÑÐÐÐÐÐ ÐÐÐÐÐÐ" |
|---|---|
| Next by Date: | Re: [PATCH 15/19] mkfs: don't treat files as though they are block devices, Eric Sandeen |
| Previous by Thread: | RE: xfs_repair couldn't verify primary superblock, StÃphane Larose |
| Next by Thread: | RE: xfs_repair couldn't verify primary superblock, StÃphane Larose |
| Indexes: | [Date] [Thread] [Top] [All Lists] |