Date: Thu, 15 Aug 2002 16:51:46 +0200
To: linux-xfs@oss.sgi.com
Cc: lvm-devel@sistina.com
Subject: Re: oops when creating an lvm-snapshot
Message-ID: <20020815145145.GD23422@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> <1029421149.11475.6.camel@jen.americas.sgi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1029421149.11475.6.camel@jen.americas.sgi.com>
User-Agent: Mutt/1.4i
From: erik@debian.franken.de (Erik Tews)
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

On Thu, Aug 15, 2002 at 09:19:09AM -0500, Steve Lord wrote:
> 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?
> 
> A complete stack backtrace would help here, I do not have LVM setup
> right now.
> 
> In your second message you say it oopses after a reboot, I presume
> you mean it oopses mounting the snapshot in the same location as
> in the first case?
> 
> Details please, details!

OK, will generate the backtrace tomorrow

And yes, it first crashed when I did mount /dev/master/xfs-snapshot
/snap