xfs
[Top] [All Lists]

Re: cannot mount snapshot

To: ASANO Masahiro <masano@xxxxxxxxxxxxxx>
Subject: Re: cannot mount snapshot
From: Nathan Scott <nathans@xxxxxxx>
Date: Fri, 14 Sep 2001 11:14:30 +1100
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20010913224933W.masano@xxxxxxxxxxxxxx>; from masano@xxxxxxxxxxxxxx on Thu, Sep 13, 2001 at 10:49:33PM +0900
References: <20010913224933W.masano@xxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
hi,

On Thu, Sep 13, 2001 at 10:49:33PM +0900, ASANO Masahiro wrote:
> Hi,
> 
> I cannot mount the snapshot filesystem of the XFS filesystem.
> To make the snapshot, I used xfs_freeze. Why it couldn't be mounted?
> 
>   # lvcreate -L 132m -n masano1 vg0
>   # mkfs.xfs /dev/vg0/masano1
>   # mount -t xfs /dev/vg0/masano1 /mnt/masano1
>   # xfs_freeze -f /mnt/masano1
>   # lvcreate -L 60m -n masano2 -s /dev/vg0/masano1 
>   # xfs_freeze -u /mnt/masano1
>   # mount -t xfs -o ro,nouuid /dev/vg0/masano2 /mnt/masano2
> 
>   XFS mounting filesystem lvm(58,1)
>   XFS: WARNING: recovery required on readonly filesystem.
>   XFS: write access unavailable, cannot proceed.

For some reason the block device beneath the filesystem is
marked as readonly, and XFS cannot do anything about that.

In particular - the "write access unavailable" message comes
from fs/xfs/linux/xfs_lrw.c in the xfs_is_read_only() routine.
This routine uses the block devices is_read_only() routine in
drivers/block/ll_rw_blk.c to see if the device is going to
allow writes.

In your case, it seems the driver has marked /dev/vg0/masano1
as readonly (I don't know why that would be - looks like LVM).
Which means XFS cannot proceed because it cannot do recovery
on a readonly device.

Hope this helps.

>   XFS: log mount/recovery failed
>   XFS: log mount failed
> 
> I noticed this may be occurred from "8/28 Merge irix6.5f:irix:101630a".
> Any comments and suggestions are welcome.
> 
> Cheers.
> 
> --
> masano
> 

-- 
Nathan


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