|Subject:||Re: XFS - bad primary superblock - bad magic number !!!|
|From:||Panagiotis Atmatzidis <p.atmatzidis@xxxxxxxxx>|
|Date:||Sun, 18 Jun 2006 12:30:44 +0300|
|Domainkey-signature:||a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=ODFq+TwulHS3bCJAzvyRC41Ad5p31c5TcDcGzQCnbUoOjCyXI+lSg/cpQzT2+RIrMgWCWwP2yQr+93FLsDu3UNYWKk1SWrbstVonNP0zgGUTFXSfdyLBAYp6b3DrgfkkQb/XzKoJIIJDIOcshvo4+bVPt0rfpK+LEEHzZHlukio=|
|User-agent:||Thunderbird 18.104.22.168 (Macintosh/20060530)|
On Fri, 16 Jun 2006, Panagiotis Atmatzidis wrote:#xfs_repair -n /dev/mapper/enc-a Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!!Maybe the crypto setup failed and /dev/mapper/enc-a has not been decrypted. What does$ dd if=/dev/mapper/enc-a bs=1k count=20 | less or $ dd if=/dev/mapper/enc-a bs=1k count=20 | file -show you? Here I can "less" through something which appears to an XFS header, ater this I can even see filecontents. The 2nd command should show sth. like "SGI XFS filesystem data".And don't forget to use a current kernel/xfsprogs before doing sth. with the FS....
Hello,Thank you for the reply. You are probably right. After the third reboot the 3 filesystems seem to be working as usual (which is fine) and nothing appears to be corrupted in any way. I'm not really sure about what happened but, it could be the encryption.
Thank you, Best Regards
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||TAKE 904196 - Merge up to 2.6.17, Nathan Scott|
|Next by Date:||SW RAID 5 Bug? - Slow After Rebuild (XFS+22.214.171.124), Justin Piszcz|
|Previous by Thread:||Re: XFS - bad primary superblock - bad magic number !!!, christian|
|Next by Thread:||Need SW RAID5 & mkfs.xfs help with chunksize & swidth/su respectively, Justin Piszcz|
|Indexes:||[Date] [Thread] [Top] [All Lists]|