Well, one way or another you got block 0 clobbered...
I'm guessing that perhaps xfs_repair is finding an older superblock from
your previous mkfs, and getting confused. I'd let repair run to
completion and see if it finds other superblocks that are valid...
that's my best suggestion for now.
On Wed, 2004-03-10 at 10:53, Errikos Pitsos {secure} wrote:
> the machine has three partitions.
> 1 boot
> 2 swap
> 3 root
>
> it's a laptop hd.
>
> I took it out of the one laptop and put it into another because I wanted
> to transfer 50gb onto it and because I wanted to change partition 2 and
> 3. So resized 2 and 3, which naturally deleted the data on both of them.
I hope you re-ran mkfs at this point?
> Mounted part3 and copied 50gb of data onto it. Then I shutdown the
> machine(where I didn't find a syslog entry for the xfs part being
> properly unmounted, don't know whether this is normally always logged)
No, xfs doesn't log clean unmounts in the syslog.
> and put the hd back into the original laptop. She booted fine, grub,
> everything, but during kernel loading isn't able to mount the xfs.
> partition(root) I took the hd out again and tried mounting the hd on the
> system where I had copied the stuff from. Nothing works there either, so
> that's where I am now.
I assume that if you repartitioned part3 (root), you probably also
re-ran your bootloader. Again, did you tell the bootloader to land on
the mbr, or on a partition?
-Eric
> e
>
>
> Eric Sandeen {u} wrote:
> > Any chance you put your bootloader on the root partition, rather than
> > the mbr? XFS uses block zero, as would the bootloader if you put it
> > there.
> >
> > Still, not sure offhand why repair did not fix things up.
> >
> > On Wed, 2004-03-10 at 02:27, Errikos Pitsos {secure} wrote:
> >
> >>Hi!
> >>
> >>Seems like I ran into a known problem wrt to "unable to verify
> >>superblock, continuing..."
> >>http://oss.sgi.com/projects/xfs/faq.html#xfsmountfail
> >>
> >>I can't mount the xfs fs.
> >>I can't repair the xfs fs.
> >>Yes, this is my root partition, this is a new system I was setting up.
> >>I don't know what caused the trouble, but it seems that somehow the
> >>system was not properly unmounted.
> >>Using xfs_repai without "L" doesn't change anything.
> >>So if I can help finding that bug tell me.
> >>I am using Gentoo and had a 2.4.24-xfs-r3 on there, syslog says:
> >>Mar 10 07:56:43 leonzwei SGI XFS snapshot-2.4.23-2003-12-01_00:33_UTC
> >>with no debug enabled
> >>
> >>For some reason it seems that the XFS was not cleanly unmounted, not
> >>sure though. The system was cleanly shutdown, but I didn't find a:
> >> Mar 10 03:47:25 leonzwei Ending clean XFS mount for filesystem: ide1(22,3)
> >>
> >>in there which I had before.
> >>
> >>
> >>syslog shows these here when I try to mount the partition.
> >>Mar 10 08:03:37 leonzwei XFS: bad magic number
> >>Mar 10 08:03:37 leonzwei XFS: SB validate failed
> >>
> >>
> >>
> >>here some console output:
> >>
> >>leonzwei root # xfs_repair -nLv /dev/hdc3
> >>Phase 1 - find and verify superblock...
> >>bad primary superblock - bad magic number !!!
> >>
> >>attempting to find secondary superblock...
> >>...........................................................................................................
> >>
> >>
> >>
> >>.....................found candidate secondary superblock...
> >>error reading superblock 54 -- seek to offset 57982058496 failed
> >>unable to verify superblock, continuing...
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>.............................................................found
> >>candidate secondary superblock...
> >>error reading superblock 54 -- seek to offset 57982058496 failed
> >>unable to verify superblock, continuing...
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>...........................................................................................................
> >>
> >>
> >>
> >>.............................................................found
> >>candidate secondary superblock...
> >>error reading superblock 54 -- seek to offset 57982058496 failed
> >>unable to verify superblock, continuing...
> >>
> >>
> >>goes on for ever.
> >>
> >>here something else that I saw that you requested from somebody who had
> >>the same bug:
> >>
> >>leonzwei root # xfs_db /dev/hdc3
> >>xfs_db: unexpected XFS SB magic number 0x1917d8b3
> >>xfs_db: sb 0
> >>xfs_db: p
> >>magicnum = 0x1917d8b3
> >>blocksize = 689553475
> >>dblocks = 12180848741608851668
> >>rblocks = 8457844901802481315
> >>rextents = 17089333805017595916
> >>uuid = c005688d-587d-e4b5-7729-c2cd4e81e350
> >>logstart = 12437974581420056107
> >>rootino = 2035592538136216092
> >>rbmino = 2311019282328682982
> >>rsumino = 940638864488651459
> >>rextsize = 4062341194
> >>agblocks = 1795335310
> >>agcount = 3583083788
> >>rbmblocks = 745776455
> >>logblocks = 2344638215
> >>versionnum = 0xcd77
> >>sectsize = 57419
> >>inodesize = 22122
> >>inopblock = 22912
> >>fname = "q\275\347\017o;\202\376<l\243I"
> >>blocklog = 253
> >>sectlog = 155
> >>inodelog = 111
> >>inopblog = 173
> >>agblklog = 91
> >>rextslog = 155
> >>inprogress = 45
> >>imax_pct = 183
> >>icount = 3536497887666359542
> >>ifree = 15647017454152257949
> >>fdblocks = 15766340045555572059
> >>frextents = 7127039695291382717
> >>uquotino = 7880036713507589276
> >>gquotino = 3559299706880429710
> >>qflags = 0x5d07
> >>flags = 0xe9
> >>shared_vn = 152
> >>inoalignmt = 237542219
> >>unit = 2706140452
> >>width = 574901660
> >>dirblklog = 54
> >>logsectlog = 60
> >>logsectsize = 49029
> >>logsunit = 1105637059
> >>xfs_db:
> >>
> >>
> >>anything else I can provide bug hunters with?
> >>
> >>erik
--
Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc. 651-683-3102
|