3Ware delayed device mounting errors with newer 9500 series adapters
Adam,
We have been getting 3Ware 9500 series adapters in the past 60 days which exhibit a delayed behavior during mounting of FS from/etc/fstab. The adapters older than this do not exhibit this behavior.
During bootup, if the driver is compiled as a module rather than in kernel, mount points such as /var in fstab fail to detect the devices until the system fully boots, at which point the /dev/sdb etc. devices showup. It happens on both ATA cabled drives and drives cabled with multi-lane controller backplanes.
The problem is easy to reproduce. Install ES4, point the /var directory during install to one of the array devices in disk druid, and after the install completes, /var/ will not mount during bootup and all sorts of errors stream off the screen. I can reproduce the problem with several systems in our labs and upon investigating the adapter revisions, I find that adapters ordered in the past 60 days exhibit
the problem. Compiling the driver in kernel gets around the problem, indicating its timing related.
Jeff
Quoted 13 lines · On Sat, 21 Oct 2006 11:03:10 -0600 "Jeffrey V. Merkey"…
Adam,
We have been getting 3Ware 9500 series adapters in the past 60 days which exhibit a delayed behavior during mounting of FS from
/etc/fstab. The adapters older than this do not exhibit this behavior.During bootup, if the driver is compiled as a module rather than in kernel, mount points such as /var in fstab fail to detect the devices until the system fully boots, at which point the
/dev/sdbetc. devices showup. It happens on both ATA cabled drives and drives cabled with multi-lane controller backplanes.
Quoted 9 lines
The problem is easy to reproduce. Install ES4, point the /var directory during install to one of the array devices in disk druid, and after the install completes,
/var/will not mount during bootup and all sorts of errors stream off the screen. I can reproduce the problem with several systems in our labs and upon investigating the adapter revisions, I find that adapters ordered in the past 60 days exhibit
the problem. Compiling the driver in kernel gets around the problem,
indicating its timing related.
cc's added.
Jeff,
Can you reproduce with 2.6.18.1? ES4 contains a custom 3ware driver.
Also, you have included no error output with this email whatsoever. Can you go to a virtual console during your ES4 install, run 'dmesg', and see if the errors are in there, or if they are a part of the ES4 anaconda installer?
/dev/sdb, etc. having delayed appearances sounds like it is udev related.
Are you running the latest firmware? Do your controllers older than 60 days have different firmware?
I will try to reproduce this.
-Adam
Quoted 32 lines · Andrew Morton
Quoted 13 lines · On Sat, 21 Oct 2006 11:03:10 -0600 "Jeffrey V. Merkey"…
Adam,
We have been getting 3Ware 9500 series adapters in the past 60 days which exhibit a delayed behavior during mounting of FS from
/etc/fstab. The adapters older than this do not exhibit this behavior.During bootup, if the driver is compiled as a module rather than in kernel, mount points such as /var in fstab fail to detect the devices until the system fully boots, at which point the
/dev/sdbetc. devices showup. It happens on both ATA cabled drives and drives cabled with multi-lane controller backplanes.Quoted 9 lines
The problem is easy to reproduce. Install ES4, point the /var directory during install to one of the array devices in disk druid, and after the install completes,
/var/will not mount during bootup and all sorts of errors stream off the screen. I can reproduce the problem with several systems in our labs and upon investigating the adapter revisions, I find that adapters ordered in the past 60 days exhibit
the problem. Compiling the driver in kernel gets around the problem,
indicating its timing related.cc's added.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 3 lines · adam radford
Jeff,
Can you reproduce with 2.6.18.1? ES4 contains a custom 3ware driver.
We don't use kernels later than 2.6.15 in our shipping releases since they have some issues with stability.
Quoted 4 lines
Also, you have included no error output with this email whatsoever. Can you go to a virtual console during your ES4 install, run 'dmesg', and see if the errors are in there, or if they are a part of the ES4 anaconda installer?
dmesg produces no output since the errors are reflected from init.
Errors are typical of an unmounted volume. i.e.
"cannot touch /var/lock/subsys/<service> (dozens of these) Starting System logger (hangs for 15 minutes)
So no logs .....
Quoted 2 lines
/dev/sdb, etc. having delayed appearances sounds like it is udev related.
No, I do not believe so.
Quoted 3 lines
Are you running the latest firmware? Do your controllers older than 60 days have different firmware?
This is the right question. I will collect the various versions this occurs on and post them here.
Quoted 2 lines
I will try to reproduce this.
Pretty easy to do.
Jeff
Quoted 41 lines
-Adam
Quoted 35 lines · Andrew Morton
Quoted 6 lines · On Sat, 21 Oct 2006 11:03:10 -0600 "Jeffrey V. Merkey"…
Adam,
We have been getting 3Ware 9500 series adapters in the past 60 days which exhibit a delayed behavior during mounting of FS from
/etc/fstab. The adapters older than this do not exhibit thisbehavior.
Quoted 8 lines
During bootup, if the driver is compiled as a module rather than in kernel, mount points such as /var in fstab fail to detect the devices until the system fully boots, at which point the
/dev/sdbetc. devices showup. It happens on both ATA cabled drives and drives cabled with multi-lane controller backplanes.The problem is easy to reproduce. Install ES4, point the /var
directory
Quoted 2 lines
during install to one of the array devices in disk druid, and after the install completes,
/var/will not mount during bootup and allsorts
Quoted 6 lines
of errors stream off the screen. I can reproduce the problem with several systems in our labs and upon investigating the adapter revisions, I find that adapters ordered in the past 60 days exhibit
the problem. Compiling the driver in kernel gets around the problem,
indicating its timing related.cc's added.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html