From: Hamid <spam.wax@gmail.com>
To: Stefan Smietanowski <stesmi@stesmi.com>
Cc: Timothy Shimmin <tes@sgi.com>, Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com
Subject: Re: XFS: SB validate failed
Date: Sun, 01 Jun 2008 03:35:36 -0400 [thread overview]
Message-ID: <48425148.1080105@gmail.com> (raw)
In-Reply-To: <48409981.1050405@stesmi.com>
> I think you have the terminology a little mixed up.
>
> If you mount a something without supplying -o loop "mount" will assume
> the filesystem resides in a DEVICE.
>
> If you mount a something WHILE supplying -o loop you tell "mount" that
> it should mount it using a loop device. Note device here, it's trickery
> really as what it does is that "mount" will FIRST create a new device
> node "/dev/loop0" for example and then it will mount from that device
> node.
>
Thanks Stefan, Now it makes real sense.
I guess I am back to my original question:
What does 'SB validate failed' indicate and what it really means to my
case ?
fdisk reports the structure of the Jaz disk as:
$ sudo fdisk -ul jaz7.img
Disk jaz7.img (SGI disk label): 255 heads, 63 sectors, 0 cylinders
Units = sectors of 1 * 512 bytes
----- partitions -----
Pt# Device Info Start End Sectors Id System
8: jaz7.img1 3072 2091007 2087936 a SGI xfs
9: jaz7.img2 0 3071 3072 0 SGI volhdr
11: jaz7.img3 0 2091007 2091008 6 SGI volume
----- Bootinfo -----
Bootfile: /unix
----- Directory Entries -----
0: sgilabel sector 3 size 512
I went ahead and tried to mount Partition 8 from image using the offset
and loop options of the mount command:
$ sudo mount -t xfs -o loop,offset=$((512*3072)) jaz7-partition.img /mnt
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
And system log says:
XFS: bad magic number
XFS: SB validate failed
So I am guessing I have one of these 3 cases:
1- Bad partition table, good file system
2- Good partition table, corrupt file system
3- Or both gone south!!!
I checked the man pages of 'vh' on Irix. It seems that the volhdr
partition is 'usually' 2 megabytes but the disk in question has 3072*512
bytes ?
Can this be a sign of corruption ?
So where would you start looking at if you wanted to fix this problem ?
Partition table or the file system ?
next prev parent reply other threads:[~2008-06-01 7:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 17:05 XFS: SB validate failed Spam Magnet
2008-05-29 17:19 ` Eric Sandeen
2008-05-29 19:55 ` Spam Magnet
2008-05-29 20:02 ` Eric Sandeen
2008-05-29 21:00 ` Spam Magnet
2008-05-29 21:06 ` Eric Sandeen
2008-05-29 21:46 ` Spam Magnet
2008-05-29 22:19 ` Eric Sandeen
2008-05-29 22:25 ` Stefan Smietanowski
2008-05-30 5:28 ` Timothy Shimmin
2008-05-30 17:19 ` Spam Magnet
2008-05-30 17:59 ` Stefan Smietanowski
2008-05-30 23:26 ` Hamid
2008-05-31 0:19 ` Stefan Smietanowski
2008-05-31 0:22 ` Stefan Smietanowski
2008-06-01 7:35 ` Hamid [this message]
2008-06-01 10:46 ` Stefan Smietanowski
2008-06-03 17:36 ` Spam Magnet
2008-06-03 17:56 ` Spam Magnet
2008-06-03 18:59 ` Stefan Smietanowski
2008-06-03 19:39 ` Spam Magnet
2008-06-03 20:23 ` Stefan Smietanowski
2008-06-05 16:16 ` Spam Magnet
2008-06-02 2:08 ` Timothy Shimmin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48425148.1080105@gmail.com \
--to=spam.wax@gmail.com \
--cc=sandeen@sandeen.net \
--cc=stesmi@stesmi.com \
--cc=tes@sgi.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.