• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: XFS mount error: can't read superblock  (Read 12016 times)
rooster
Guest
« on: May 07, 2009, 02:57:05 AM »

Hi,

I am using Marvell git (2.6.30-rc3) with Jaunty, formatted my sda1 to XFS with not problem, copy content to it done with no problems.

Then I umounted it and tried to mount it again, this is what I get:
Quote
mount: /dev/sda1: can't read superblock

When running xfs_check I get this:
Quote
xfs_check /dev/sda1
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_check.  If you are unable to mount the filesystem, then use
the xfs_repair -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.

So then I ran xfs_repair:
Quote
root@plugme:~# xfs_repair /dev/sda1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair.  If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.

Only xfs_repair with "-L" option fixed the XFS mount:
Quote
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
ALERT: The filesystem has valuable metadata changes in a log which is being
destroyed because the -L option was used.
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done

Now I can mount it and see my stuff, monting and umounting it works fine until I copy content to the partition.

Is there some mkfs/mount option that fixes this? I see some XFS EABI related issues on Lenny too.

When creating the XFS with log on another device solves this problem:
Quote
mkfs.xfs  -l logdev=/dev/sda2,size=10000b /dev/sda1
mount /dev/sda1 /mnt/disk/ -o logdev=/dev/sda2
« Last Edit: May 07, 2009, 03:14:06 AM by rooster » Logged

Raśl Porcel
Global Moderator
Jr. Member
*****

Karma: 0
Posts: 68


View Profile
« Reply #1 on: May 07, 2009, 08:38:39 AM »

As far as i've been told, XFS doesn't work well on ARM.
Logged

rooster
Guest
« Reply #2 on: May 07, 2009, 12:06:43 PM »

it used to work perfect on LSP version (2.6.22.18), for some reason it fails to work properly on 2.6.30-rc3.
Logged

Pages: [1]
Print
Jump to: