[opensuse] created new disk array, partitioned w/parted, but cannot mkfs.xfs: dev busy??
How can a raw disk partition be busy? I am able to read/write to it with 'dd': time dd if=/dev/sdd1 of=/dev/null bs=16M count=128 2147483648 bytes (2.1 GB) copied, 5.70285 s, 377 MB/s 5.72sec 0.00usr 2.21sys (38.77% cpu)
time dd if=/dev/zero of=/dev/sdd1 bs=16M count=128 2147483648 bytes (2.1 GB) copied, 7.65681 s, 280 MB/s 7.66sec 0.00usr 2.82sys (36.94% cpu)
I've never seen an unformatted raw partition on a disk be busy before...? lsof & fuser turned up nada... FWIW, I'm trying to create a new rootdisk that can hold root+usr+usrshare Maybe this is a sign that I'm being drawn toward the wrong path.... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-06-26 09:40, Linda Walsh wrote:
How can a raw disk partition be busy?
I am able to read/write to it with 'dd': time dd if=/dev/sdd1 of=/dev/null bs=16M count=128 2147483648 bytes (2.1 GB) copied, 5.70285 s, 377 MB/s 5.72sec 0.00usr 2.21sys (38.77% cpu)
time dd if=/dev/zero of=/dev/sdd1 bs=16M count=128 2147483648 bytes (2.1 GB) copied, 7.65681 s, 280 MB/s 7.66sec 0.00usr 2.82sys (36.94% cpu)
I've never seen an unformatted raw partition on a disk be busy before...?
What command tells you that it is busy? How are you doing it? Maybe the desktop attempts to automount it, so try in level 3, or with a non-clever desktop. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWNHJQACgkQja8UbcUWM1wbugEAlejZHCo8U/w58Ttp4HGxw9DN fFzERBvTIblFYQ7SZ6UA+wbCjlkilGBDCHYkG/2R9zJumaOlf/njxJqV1togwscA =yZ0K -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 6/26/2015 2:34 AM, Carlos E. R. wrote:
What command tells you that it is busy? How are you doing it? Maybe the desktop attempts to automount it, so try in level 3, or with a non-clever desktop.
--- the "mkfs.xfs" command claimed it was busy (as run from an 'ssh' session -- no desktop". Rebooting was required to clear the problem state -- which is rather bothersome. But now, I'm getting blinking 'orange' fault lights in the drive trays where the new drives are -- even though the LSI Megaraid management SW, claims they are in good health. Message on the front LCD says that all of them have a "fault", and to review and clear the SEL (System Event Log). Coincidentally I just figured out how to list and clear the the SEL using ipmiutil -- that doesn't seem to clear the fault-- rebooting does... for about 3 minutes... then the fault is reasserted. Meanwhile, I can partition the new drive and had the LSI SW do a complete consistency check -- came up fine. I have a icky feeling that it's a bug or problem in the system bios, but I checked and there are no newer ones. Very weird. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-06-28 13:15, Linda Walsh wrote:
On 6/26/2015 2:34 AM, Carlos E. R. wrote:
What command tells you that it is busy? How are you doing it? Maybe the desktop attempts to automount it, so try in level 3, or with a non-clever desktop.
--- the "mkfs.xfs" command claimed it was busy (as run from an 'ssh' session -- no desktop".
But was a desktop running somewhere else, on that machine?
Rebooting was required to clear the problem state -- which is rather bothersome.
But now, I'm getting blinking 'orange' fault lights in the drive trays where the new drives are -- even though the LSI Megaraid management SW, claims they are in good health.
Oh. Maybe it was busy building the raid? On reboot, you destroyed the process and now the array is in a faulty state. Just a wild guess... - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlWP304ACgkQja8UbcUWM1z9yQD+JR6ws3puWFBbQHJ9hxwrTKby SJNBnIketyxw956neGsBAINfubFSMVehNTiepGTyLMP5YfMyaUWKwaCbOCGYIY8U =uGiR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 6/28/2015 4:49 AM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2015-06-28 13:15, Linda Walsh wrote:
On 6/26/2015 2:34 AM, Carlos E. R. wrote:
What command tells you that it is busy? How are you doing it? Maybe the desktop attempts to automount it, so try in level 3, or with a non-clever desktop.
--- the "mkfs.xfs" command claimed it was busy (as run from an 'ssh' session -- no desktop". But was a desktop running somewhere else, on that machine?-
Nope. Sole user. It doesn't have separate graphics card (1024x768x32 colors or 1280x1024x16 colors...
Rebooting was required to clear the problem state -- which is rather bothersome.
But now, I'm getting blinking 'orange' fault lights in the drive trays where the new drives are -- even though the LSI Megaraid management SW, claims they are in good health. Oh. Maybe it was busy building the raid? On reboot, you destroyed the process and now the array is in a faulty state. Just a wild guess...
I let the LSI megaraid monitor program finish doing a full initialization -- not a fast one... took about 1.5 hours for a 250GB RAID-10 (4 x125). I wanted to test the disks -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Carlos E. R. -
Linda Walsh