From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4)
Description of problem:
Bordeaux with qa1129 (2.4.9-17.3smp) installed, direct-attached qlogic2200
storage, and using new qla2200 driver.
After rebooting, attached storage partition and filesystem cannot be
mounted -- "mount: /dev/sde1 is not a valid block device"
I tried unloading and reloading the driver manually, still didn't work.
If you remake the partition table in parted (mklabel) and recreate the
partition, then you can mount it.
Reboot again, and it's not a valid block device.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install qa1129 on a bordeaux w/ direct attached qlogic2200 storage.
2. Create a partition and filesystem on a lun. Mount it successfully.
3. Reboot and note inability to mount. Remake partition table and
partition to be able to mount again.
Actual Results: Lun partition is not a valid block device after reboot.
Expected Results: Should mount.
I've seen this before but cannot reproduce it with the current driver (2.4.9-17.4)
Reproduced w/ 2.4.9-17.4smp
>Additional comment by email@example.com
>I've seen this before but cannot reproduce it with the current driver >(2.4.9-17.4)
>Additional comment by firstname.lastname@example.org
>Reproduced w/ 2.4.9-17.4smp
Does it happen every time now? If not, can you characterize this?
I just tried this 4 times (fdisk /dev/sdX, make partition, mke2fs, mount, put
file on, umount, reboot) and I could mount and read the file just fine after
To clarify, our tests were done with a PV650 direct-attached. We did
the same tests earlier using the switched fabric. We could not
reproduce the problem with either setup. Sounds like we need more
explicit setup information; we have duplicated as exactly as we can,
with no luck reproducing it.
Ever since I created partitions, filesystems, and mounted all ten luns on my
attached storage I have not been able to reproduce this. Several reboots and
different combinations of mounting and rebooted, and still nothing. I have not
see this since the very first check after installing 2.4.9-17.4smp. I will keep
an eye out for this, but it appears to be all but gone.
So the first boot must have been a leftover from the previous kernel.
I'll close this; re-open it if you see it again with 17.4 or later.