From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3EF69479.7060709@sina.com>
From: more <more0401@sina.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [linux-lvm] problem of snapshot on XFS
Sender: linux-lvm-admin@sistina.com
Errors-To: linux-lvm-admin@sistina.com
Reply-To: linux-lvm@sistina.com
List-Help: <mailto:linux-lvm-request@sistina.com?subject=help>
List-Post: <mailto:linux-lvm@sistina.com>
List-Subscribe: <http://lists.sistina.com/mailman/listinfo/linux-lvm>,
	<mailto:linux-lvm-request@sistina.com?subject=subscribe>
List-Unsubscribe: <http://lists.sistina.com/mailman/listinfo/linux-lvm>,
	<mailto:linux-lvm-request@sistina.com?subject=unsubscribe>
List-Archive: <http://lists.sistina.com/pipermail/linux-lvm/>
Date: Mon Jun 23 00:48:01 2003
List-Id: <linux-lvm.redhat.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: linux-lvm@sistina.com

Hi,

I am using XFS on LVM1 now.

I build snapshot LV using xfs_freeze and not using norecovery mount 
option. This is commended in lvm-howto.
But in my test, if I reboot the system in the progress of file writing 
on a LV that has snapshot,  the next time mounting snapshot will report 
XFS error and the system wants to repair the snapshot. So I will have to 
use norecovery option now.

I feel puzzled that why XFS repairing is needed on snapshot, I am now 
building an enterprise network file server, the robust is very important 
for us.

Very thanks for any feeding, by the way, it is not possible for me to 
use LVM2 in current.


Regards,
more