Messages in this thread | | | Date | Sat, 16 Mar 2002 19:43:20 -0800 (PST) | From | dean gaudet <> | Subject | Re: /dev/md0: Device or resource busy |
| |
On Sun, 17 Mar 2002, Alan Cox wrote:
> > i just tried a "linux init=/bin/sh" boot, and it's still saying Device or > > resource busy: > > > > init-2.05a# raidstop /dev/md0 > > md: md0 still in use. > > /dev/md0: Device or resource busy > > init-2.05a# mount /proc > > Duplicated. Seems the md code deos indeed have a bug there
ACK! sorry. it's not the kernel code, it's raidstop. it seems to open /dev/md0 an extra time for what reason i'm not sure. it even does it when you're referring to other md devices. for example:
# strace raidstop /dev/md3 ... open("/dev/md0", O_RDONLY) = 4 ioctl(4, 0x800c0910, 0x804fd1c) = 0 open("/dev/md3", O_RDWR) = 5 fstat64(5, {st_mode=S_IFBLK|0660, st_rdev=makedev(9, 3), ...}) = 0 ioctl(5, 0x932, 0) = 0 ...
mdctl doesn't have this problem.
fwiw dpkg tells me i've got raidtools 0.90.20010914-9
-dean
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |