Subject: Re: [lvm-devel] Re: oops when creating an lvm-snapshot
From: Eric Sandeen <sandeen@sgi.com>
To: "lvm-devel@sistina.com" <lvm-devel@sistina.com>
Cc: linux-xfs@oss.sgi.com, Erik Tews <erik@debian.franken.de>
In-Reply-To: <20020815104938.GB23422@no-maam.dyndns.org>
References: <20020814170120.GA23422@no-maam.dyndns.org>
	<1029344832.15672.90.camel@jen.americas.sgi.com>
	<20020814183631.A21357@infradead.org> 
	<20020815104938.GB23422@no-maam.dyndns.org>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 15 Aug 2002 13:35:00 -0500
Message-Id: <1029436500.30024.2.camel@stout.americas.sgi.com>
Mime-Version: 1.0
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

Ok, the problem now is that Erik was not using -o ro when he tried to
mount, and LVM rightly returned EACCES - but then we mishandled the
error and oopsed.  oops!  Mounting with -o ro avoids the oops, and I
have a fix here for the error return that I'll check in shortly.

-Eric

On Thu, 2002-08-15 at 05:49, Erik Tews wrote:
> Ok, I fetched your patch from cvs today. Snapshot seems to work fine,
> but I cannot mount the snapshot. I did a mount -o nouuid
> /dev/master/xfssnap /snap and at this moment my kernel oopsed. The
> backtrace shows me that the oops happens in xfs_statfs which was called
> by linvfs_read_super which was called by get_sb_bdev. Can you reproduce
> this and do you know what happened?

-- 
Eric Sandeen      XFS for Linux     http://oss.sgi.com/projects/xfs
sandeen@sgi.com   SGI, Inc.         651-683-3102