mkfs.ext3: Permission denied while trying to determine filesystem size
Justin Conover
justin.conover at gmail.com
Sun May 29 20:26:05 UTC 2005
On 5/29/05, Justin Conover <justin.conover at gmail.com> wrote:
> Can't create a logical volume, have no problems doing it on another
> rawhide box. Plenty of space, I've done this ++++ times and for some
> reason this box is just causing a problem. "permission denied"
>
> Could this be a dieing HD? The box has 4x36GB scsi drives in it, in
> Raid0/lvm config.
>
>
> [root at trinity ~]# lvcreate -L2G -nLogVol08 VolGroup01
> Logical volume "LogVol08" created
> [root at trinity ~]# mke2fs -j /dev/VolGroup01/LogVol08
> mke2fs 1.37 (21-Mar-2005)
> Could not stat /dev/VolGroup01/LogVol08 --- Permission denied
> [root at trinity ~]# mkfs.ext3 -F -j /dev/VolGroup01/LogVol08
> mke2fs 1.37 (21-Mar-2005)
> mkfs.ext3: Permission denied while trying to determine filesystem size
> # mkfs.ext3 -F -j /dev/mapper/VolGroup01-LogVol08
> mke2fs 1.37 (21-Mar-2005)
> mkfs.ext3: Permission denied while trying to determine filesystem size
> ]# mkfs.ext3 -F -j /dev/mapper/VolGroup01-LogVol08
> mke2fs 1.37 (21-Mar-2005)
> mkfs.ext3: Permission denied while trying to determine filesystem size
> [root at trinity ~]# mke2fs -f /dev/mapper/VolGroup01-LogVol08
> mke2fs: bad fragment size - /dev/mapper/VolGroup01-LogVol08
>
> [root at trinity ~]# id -Z
> root:system_r:unconfined_t
> [root at trinity ~]# ls -la /sbin/ | grep mkfs
> -rwxr-xr-x 1 root root 7192 May 3 23:30 mkfs
> -rwxr-xr-x 1 root root 15872 May 3 23:30 mkfs.cramfs
> -rwxr-xr-x 3 root root 35888 May 10 04:17 mkfs.ext2
> -rwxr-xr-x 3 root root 35888 May 10 04:17 mkfs.ext3
> -rwxr-xr-x 3 root root 30180 Apr 28 09:31 mkfs.msdos
> -rwxr-xr-x 3 root root 30180 Apr 28 09:31 mkfs.vfat
> [root at trinity ~]# lsmod | grep ext3
> ext3 133193 8
> jbd 61785 1 ext3
>
> [root at trinity ~]# vgdisplay
> --- Volume group ---
> VG Name VolGroup01
> System ID
> Format lvm2
> Metadata Areas 1
> Metadata Sequence No 12
> VG Access read/write
> VG Status resizable
> MAX LV 0
> Cur LV 9
> Open LV 8
> Max PV 0
> Cur PV 1
> Act PV 1
> VG Size 101.28 GB
> PE Size 32.00 MB
> Total PE 3241
> Alloc PE / Size 672 / 21.00 GB
> Free PE / Size 2569 / 80.28 GB
> VG UUID 8A535T-TOpJ-Fzkg-BREJ-TJE7-E3Lp-nChZOg
>
>
> The differences on the box that work don't work are following,
>
> Works (x86_64/rawhide)
> # rpm -qa | grep lvm
> lvm2-2.01.08-1.0 <----- WHY 2?
> lvm2-2.01.08-2.1
> system-config-lvm-0.9.32-1.0
> # rpm -qa | grep e2fsprogs
> e2fsprogs-devel-1.37-4
> e2fsprogs-1.37-4.x86_64
> e2fsprogs-1.37-4.i386
>
>
>
> Doesn't work (x86/Rawhide)
> # rpm -qa | grep lvm
> lvm2-2.01.08-2.1
> system-config-lvm-0.9.32-1.0
> # rpm -qa | grep e2fsprogs
> e2fsprogs-devel-1.37-4
> e2fsprogs-1.37-4
> Both box's are in a soft raid/lvm config, Not sure why the i386 box
> defaulted to VolGroup01 but shouldn't matter in any case.
>
Well, it looks like the problem is between mkfs and selinux. The box
that works is set to
# sestatus
SELinux status: disabled
While the one that doesn't work is running selinux, so is this a bug,
can anyone else mkfs on selinux=1 box's? I haven't run into this
before and I know I have other box's running selinux that i've created
new fs on.
More information about the fedora-selinux-list
mailing list