[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.1.10.0907081424140.9159@asgard>
Date: Wed, 8 Jul 2009 14:35:41 -0700 (PDT)
From: david@...g.hm
To: linux-kernel <linux-kernel@...r.kernel.org>
Subject: partition detection problem on 2.6.29.1 and 2.6.30
I have a system that has a large number of drives in it (45), and it's had
a problem with banks of disks getting disconnected from it.
however, when I started looking into it today (after another sysadmin
worked on it for a while), I found that the system is not able to access
the partitions on the drives.
if I am reading dmesg correctly it is seeing the partitions during boot,
and if I do 'fdisk -l' it lists all the paritions correctly, but if I try
to do a
dd if=/dev/sdb1 of=/dev/null count=1
I get the error "dd: opening `/dev/sdb1': No such device or address"
#ls -l /dev/sdb1
brw-rw---- 1 root disk 8, 17 Nov 7 2006 /dev/sdb1
I removed udev and setup nodes manually to eliminate any possibility that
it was a problem there.
the attachment partitions.missing.partitions is a cat of /proc/partitions
sysfs shows all the drives but none of the partitions.
if I run fdisk and do a write (which runs the ioctl to re-read the
parition table) the system detects the partition and is able to access it
until the next reboot.
what is going on here?
David Lang
View attachment "partitions.missing.partitions" of type "TEXT/PLAIN" (1554 bytes)
View attachment "dmesg.missing.partitions2" of type "TEXT/PLAIN" (60278 bytes)
View attachment "dmesg.missing.partitions" of type "TEXT/PLAIN" (70327 bytes)
Powered by blists - more mailing lists