Bug 31567 - LVM - unable to change fs type from reiserfs to ext2
Summary: LVM - unable to change fs type from reiserfs to ext2
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: lvm
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-12 21:15 UTC by Tim Clymo
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-03-12 21:48:00 UTC
Embargoed:


Attachments (Terms of Use)

Description Tim Clymo 2001-03-12 21:15:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-0.1.20 i686)


Wolverine system with latest rawhide kernel (2.4.2-0.1.19).
LVM tools updated to beta5 from SRPM at people.redhat.com/laroche
Kernel built with LVM patches from above SRPM - also changed to have
builtin - not modular - support for raid1 and reiserfs (and turn off
reiserfs extensive checking). All other options as for
kernel-2.4.2-0.1.19-i686.config
LVM - 1VG containing 1PV (8Gb RAID-1 partition md1)

Create new lvol (128Mb) and mkfs -t reiserfs -v 2 /dev/vgname/newlvol.
Mount it, and then unmount it. Now mkfs /dev/vgname/newlvol. Trying to
mount it again gives error "mount: wrong fs type, bad option, bad
superblock on /dev/vgname/newlvol,
       or too many mounted file systems"

Dmesg reports "EXT2-fs: blocksize too small for device."

A reboot will enable the device to be mounted

This doesn't happen if the device is a straight single disk partition,
although I haven't tried with a standard md device with lvm out of the loop

It does happen with LVM using a disk partition as a PV instead of a raid1
md device, indicating that this is probably an LVM issue


Reproducible: Always
Steps to Reproduce:
1. See description
2.
3.

Comment 1 Matt Wilson 2001-03-12 21:47:56 UTC
LVM will be disabled in the final version.



Note You need to log in before you can comment on or make changes to this bug.