Thursday 07 February 2008 22:35:45 Bill Davidsen napisał(a):
As you may remember, I have configured udev to associate /dev/d_* devices
with
serial numbers (to keep them from changing depending on boot module loading
sequence).
Why do you care?
Because /dev/sd* devices get swapped
Friday 08 February 2008 13:44:18 Bill Davidsen napisał(a):
This is exactly what is not clear for me: what is it that identifies
drive/partition as part of
the array? /dev/sd name? UUID as part of superblock? /dev/d_n?
If it's UUID I should be safe regardless of /dev/sd* designation?
Marcin Krol wrote:
Thursday 07 February 2008 22:35:45 Bill Davidsen napisał(a):
As you may remember, I have configured udev to associate /dev/d_* devices with
serial numbers (to keep them from changing depending on boot module loading
sequence).
Why do you care?
Because
Marcin Krol wrote:
Thursday 07 February 2008 03:36:31 Neil Brown napisał(a):
8 0 390711384 sda
8 1 390708801 sda1
816 390711384 sdb
817 390708801 sdb1
832 390711384 sdc
833 390708801 sdc1
848 390710327 sdd
849 390708801 sdd1
Tuesday 05 February 2008 21:12:32 Neil Brown napisał(a):
% mdadm --zero-superblock /dev/sdb1
mdadm: Couldn't open /dev/sdb1 for write - not zeroing
That's weird.
Why can't it open it?
Hell if I know. First time I see such a thing.
Maybe you aren't running as root (The '%' prompt is
Tuesday 05 February 2008 12:43:31 Moshe Yudkowsky napisał(a):
1. Where this info on array resides?! I have deleted /etc/mdadm/mdadm.conf
and /dev/md devices and yet it comes seemingly out of nowhere.
/boot has a copy of mdadm.conf so that / and other drives can be started
and then
Marcin Krol wrote:
Tuesday 05 February 2008 21:12:32 Neil Brown napisał(a):
% mdadm --zero-superblock /dev/sdb1
mdadm: Couldn't open /dev/sdb1 for write - not zeroing
That's weird.
Why can't it open it?
Hell if I know. First time I see such a thing.
Maybe you aren't running as root (The
On Wednesday February 6, [EMAIL PROTECTED] wrote:
Maybe the kernel has been told to forget about the partitions of
/dev/sdb.
But fdisk/cfdisk has no problem whatsoever finding the partitions .
It is looking at the partition table on disk. Not at the kernel's
idea of partitions, which
Wednesday 06 February 2008 11:11:51 Peter Rabbitson napisał(a):
lsof /dev/sdf1 gives ZERO results.
What does this say:
dmsetup table
% dmsetup table
vg-home: 0 61440 linear 9:2 384
Regards,
Marcin Krol
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
Marcin Krol wrote:
Hello everyone,
I have had a problem with RAID array (udev messed up disk names, I've had
RAID on
disks only, without raid partitions)
Do you mean that you originally used /dev/sdb for the RAID array? And now you
are using /dev/sdb1?
Given the system seems confused I
Wednesday 06 February 2008 12:22:00:
I have had a problem with RAID array (udev messed up disk names, I've had
RAID on
disks only, without raid partitions)
Do you mean that you originally used /dev/sdb for the RAID array? And now you
are using /dev/sdb1?
That's reconfigured now, it
Wednesday 06 February 2008 11:43:12:
On Wednesday February 6, [EMAIL PROTECTED] wrote:
Maybe the kernel has been told to forget about the partitions of
/dev/sdb.
But fdisk/cfdisk has no problem whatsoever finding the partitions .
It is looking at the partition table on disk.
On Wednesday February 6, [EMAIL PROTECTED] wrote:
% cat /proc/partitions
major minor #blocks name
8 0 390711384 sda
8 1 390708801 sda1
816 390711384 sdb
817 390708801 sdb1
832 390711384 sdc
833 390708801 sdc1
848 390710327 sdd
1. Where this info on array resides?! I have deleted /etc/mdadm/mdadm.conf
and /dev/md devices and yet it comes seemingly out of nowhere.
/boot has a copy of mdadm.conf so that / and other drives can be started
and then mounted. update-initramfs will update /boot's copy of mdadm.conf.
--
Marcin Krol said: (by the date of Tue, 5 Feb 2008 11:42:19 +0100)
2. How can I delete that damn array so it doesn't hang my server up in a loop?
dd if=/dev/zero of=/dev/sdb1 bs=1M count=10
I'm not using mdadm.conf at all. Everything is stored in the
superblock of the device. So if you
Janek Kozicki wrote:
Marcin Krol said: (by the date of Tue, 5 Feb 2008 11:42:19 +0100)
2. How can I delete that damn array so it doesn't hang my server up in a
loop?
dd if=/dev/zero of=/dev/sdb1 bs=1M count=10
This works provided the superblocks are at the beginning of the
component
Moshe Yudkowsky wrote:
Michael Tokarev wrote:
Janek Kozicki wrote:
Marcin Krol said: (by the date of Tue, 5 Feb 2008 11:42:19 +0100)
2. How can I delete that damn array so it doesn't hang my server up
in a loop?
dd if=/dev/zero of=/dev/sdb1 bs=1M count=10
This works provided the
Michael Tokarev wrote:
Janek Kozicki wrote:
Marcin Krol said: (by the date of Tue, 5 Feb 2008 11:42:19 +0100)
2. How can I delete that damn array so it doesn't hang my server up in a loop?
dd if=/dev/zero of=/dev/sdb1 bs=1M count=10
This works provided the superblocks are at the
On Tuesday February 5, [EMAIL PROTECTED] wrote:
% mdadm --zero-superblock /dev/sdb1
mdadm: Couldn't open /dev/sdb1 for write - not zeroing
That's weird.
Why can't it open it?
Maybe you aren't running as root (The '%' prompt is suspicious).
Maybe the kernel has been told to forget about the
19 matches
Mail list logo
