| To: | Adrian Head <ahead@xxxxxxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxx>, Linux XFS Mailing List <linux-xfs@xxxxxxxxxxx>, linux-lvm@xxxxxxxxxxx, ext2-devel@xxxxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: [Ext2-devel] [ahead@xxxxxxxxxxxxxx: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily] |
| From: | "Stephen C. Tweedie" <sct@xxxxxxxxxx> |
| Date: | Mon, 7 Jan 2002 16:39:07 +0000 |
| Cc: | Stephen Tweedie <sct@xxxxxxxxxx> |
| In-reply-to: | <20020105161447.K12868@xxxxxxx>; from adilger@xxxxxxxxxxxxx on Sat, Jan 05, 2002 at 04:14:47PM -0700 |
| References: | <20020105161447.K12868@xxxxxxx> |
| Sender: | owner-linux-xfs@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
Hi, On Sat, Jan 05, 2002 at 04:14:47PM -0700, Andreas Dilger wrote: > Adrian Head <ahead@xxxxxxxxxxxxxx> wrote: > > This is the full output from kdb when trying to create a snapshot on an XFS > > volume for me. > > The system is running 2.4.17 + LVM patch (relatively minor) + VFS-lock > (needed for snapshots) + 2.4.17 XFS patch, IIRC. This has been discussed > on linux-lvm and linux-xfs for a couple of days. What is strange is that > this is happening while doing an XFS snapshot, but the oops is consistently > in ext3. There are several other ext3 filesystems on the system in > question. Is XFS or LVM using current->journal_info for anything, and if so, is it being left non-zero by anyone? --Stephen |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS DMAPI file I/O, James A Goodwin |
|---|---|
| Next by Date: | Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily, Adrian Head |
| Previous by Thread: | xfsdump assertion failure, Matteo Centonza |
| Next by Thread: | Re: [Ext2-devel] [ahead@xxxxxxxxxxxxxx: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily], Steve Lord |
| Indexes: | [Date] [Thread] [Top] [All Lists] |