All of lore.kernel.org
 help / color / mirror / Atom feed
From: f1sh <dennisvarouxis@hotmail.com>
To: linux-xfs@oss.sgi.com
Subject: Unable to mount XFS partition on Sun Ultra/Linux 2.6.17 - Function not implemented
Date: Fri, 8 Dec 2006 07:41:31 -0800 (PST)	[thread overview]
Message-ID: <7759642.post@talk.nabble.com> (raw)


I've got an ailing SGI which currently doesn't boot, so I plucked the disk
out
and slotted it into my Sun box to snoop around. Unfortunately despite my
best technical and google skills I haven't been able to resolve this.

Attempting to mount the main disk partition with a simple "mount -t xfs
/dev/sda1 /mnt/sgidisk" yields only "mount: Function not implemented".

That's it, that's all I've got. Except that I know from debugging mount that
the mount
syscall raises errno 90, which goes into strerror() which returns the "not
implemented" message.

It's a SCSI disk formatted to XFS by IRIX. IRIX and linux XFS are reportedly
disk
compatible so I don't see a problem there. There's a boot partition (1), a
swap
partition (2), and the 9 and 11 partitions used for the SGI disk label.

The host system is a Sun Ultra 5 (sparc64 sun4u) with an Adaptec aix7xxx
controller, running Gentoo Linux kernel 2.6.17-r8. The kernel has been built
with SGI partition map support. I've got the aic7xxx and xfs drivers
compiled as modules and set to autoload (I've tried with built-in versions
as well and get the same result).

The kernel at this point has been compiled with debug enabled and with
CONFIG_XFS_DEBUG=y. The XFS driver confirms this in dmesg:

"SGI XFS with ACLs, security attributes, large block/inode numbers, debug
enabled
SGI XFS Quota Management subsystem"

However when I attempt the mount there's nothing emitted in
/var/log/messages.

Note the partition type says "SGI efs". However trying to mount -t efs fails
with the expected "mount: wrong fs type". (EFS compiled as a module and
modprobed).

The output from xfs_db which admittedly doesn't mean much, to me at least, 
is:

azrael ~ # xfs_db -c sb -c p /dev/sda1
magicnum = 0x58465342
blocksize = 4096
dblocks = 491395
rblocks = 0
rextents = 0
uuid = dbfdfd61-f556-1021-8e74-0800690ac5d3
logstart = 262148
rootino = 128
rbmino = 129
rsumino = 130
rextsize = 16
agblocks = 61425
agcount = 8
rbmblocks = 0
logblocks = 1000
versionnum = 0x1094
sectsize = 512
inodesize = 256
inopblock = 16
fname = "\000\000\000\000\000\000\000\000\000\000\000\000"
blocklog = 12
sectlog = 9
inodelog = 8
inopblog = 4
agblklog = 16
rextslog = 0
inprogress = 0
imax_pct = 25
icount = 35648
ifree = 1636
fdblocks = 164789
frextents = 0
uquotino = 0
gquotino = 0
qflags = 0
flags = 0
shared_vn = 0
inoalignmt = 2
unit = 0
width = 0
dirblklog = 0
logsectlog = 0
logsectsize = 0
logsunit = 0
features2 = 0

Also interesting is the output from xfs_check:

"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."

Although this indicates that the filesystems should at least be mountable.

Any help would be appreciated - what am I missing? Is there somewhere else
that the kernel and/or the xfs driver would log their debug messages?


thanks

dennis

-- 
View this message in context: http://www.nabble.com/Unable-to-mount-XFS-partition-on-Sun-Ultra-Linux-2.6.17---Function-not-implemented-tf2781318.html#a7759642
Sent from the linux-xfs mailing list archive at Nabble.com.

             reply	other threads:[~2006-12-08 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 15:41 f1sh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-08 15:32 Unable to mount XFS partition on Sun Ultra/Linux 2.6.17 - Function not implemented Dennis Varouxis
2006-12-08 16:50 ` Eric Sandeen
2006-12-10  9:04   ` Chris Wedgwood
2006-12-11 14:53     ` Eric Sandeen

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=7759642.post@talk.nabble.com \
    --to=dennisvarouxis@hotmail.com \
    --cc=linux-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.