xfs
[Top] [All Lists]

Re: mount: Unknown error 990

To: Scott Ransom <ransom@xxxxxxxxxxxxxxxxx>
Subject: Re: mount: Unknown error 990
From: Eric Sandeen <sandeen@xxxxxxx>
Date: Thu, 18 Dec 2003 09:37:20 -0600 (CST)
Cc: Nathan Straz <nstraz@xxxxxxx>, <linux-xfs@xxxxxxxxxxx>
In-reply-to: <200312171813.55480.ransom@xxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
Unfortunately that message doesn't give us much to go on...

You might try xfs_repair (possibly with -n to not actually -do- anything)
to see if it gives any info about problems on the filesystem.

Otherwise, find this code in xfs_mount.c:

        /*
         * Get and sanity-check the root inode.
         * Save the pointer to it in the mount structure.
         */
        error = xfs_iget(mp, NULL, sbp->sb_rootino, XFS_ILOCK_EXCL, &rip, 0);
        if (error) {
                cmn_err(CE_WARN, "XFS: failed to read root inode");
                goto error3;
        }

and change the cmn_err line to say:

cmn_err(CE_WARN, "XFS: failed to read root inode (%d)", error);

so we can at least see what error was returned from xfs_iget - 
that might be a hint.

-Eric

On Wed, 17 Dec 2003, Scott Ransom wrote:

> On 17 December 2003 04:50 pm, Nathan Straz wrote:
> > On Wed, Dec 17, 2003 at 12:14:25PM -0500, Scott Ransom wrote:
> > > mount: Unknown error 990
> >
> > Check dmesg for errors.
> 
> Ah.  Forgot to add this.  Sorry:
> 
> XFS mounting filesystem sda1
> XFS: failed to read root inode
> 
> Scott
> 
> -- 
> Scott M. Ransom              Address:  McGill Univ. Physics Dept.
> Phone:  (514) 398-6492                 3600 University St., Rm 338
> email:  ransom@xxxxxxxxxxxxxxxxx       Montreal, QC  Canada H3A 2T8 
> GPG Fingerprint: 06A9 9553 78BE 16DB 407B  FFCA 9BFA B6FF FFD3 2989
> 
> 


<Prev in Thread] Current Thread [Next in Thread>