Skip to contentSkip to conversation

Unable to get XFS, ext3, reiserfs & LVM to coexist happily]

Ext2-devel Stephen C. Tweedie 3 participants 3 messages Jan 7, 2002 – Jan 15, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi,

Quoted 10 lines · Andreas Dilger
Quoted 2 lines · Adrian Head

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

#2 lore raw
Quoted 14 lines · Stephen C. Tweedie

Hi,

Quoted 10 lines · Andreas Dilger
Quoted 2 lines · Adrian Head

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.

Quoted 2 lines

Is XFS or LVM using current->journal_info for anything, and if so, is it being left non-zero by anyone?

We do not touch it, there has subsequently been a crash with ext3 removed from the kernel, so I suspect this is an XFS only issue - probably memory corruption. It appears we are doing a disk write in the unlockfs callout, possibly lvm is not in a coherent state at this point and is trampling on memory it should not be.

Eric is going to remove the offending write and see if this clears it up, off the top of my head I cannot see why we need it in the unlockfs path.

Steve

Quoted 2 lines

--Stephen

Signature · 2 lines
Steve Lord                                      voice: +1-651-683-3511
Principal Engineer, Filesystem Software         email: [email protected]
#3 lore raw
In reply to Stephen C. Tweedie
Quoted 14 lines · Stephen C. Tweedie

Hi,

Quoted 10 lines · Andreas Dilger
Quoted 2 lines · Adrian Head

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.

Quoted 2 lines

Is XFS or LVM using current->journal_info for anything, and if so, is it being left non-zero by anyone?

LVM doesn't touch it.

Quoted 8 lines

--Stephen

_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

Signature · 15 lines
Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
[email protected]                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-