Hi out there! This problem is with a raid'ed device, so I feel this is the right place to ask... It goes like this: I just wanted to add a third hd to my two-way raid array. I did the following (I don't remember the exact wording of the messages, so I give only glipses of them): # init S ... runlevel S reached # umount /usr ...device busy # fuser -k /usr no processes ... ... do umount /usr # umount /usr ... device busy I wanted to copy /usr to a spare partition, then mkraid the new three-part md-/usr, then copy the data back. I use SuSE 6.0/6.1 (partly updated), stock raid of 2.2.12 kernel. I'm not using the new raid, as the old one works very well for raid0 and linear modes, which I use. Any ideas why I cannot umount /usr, while /var, /opt, /tmp and /home can be umounted just fine? This has struck me before. IIRC, the problem does not come up when I boot into runlevel 3 (the default) and then immediately switch to runlevel S. Marc -- Marc Mutz <[EMAIL PROTECTED]> http://marc.mutz.com/ University of Bielefeld, Dep. of Mathematics / Dep. of Physics PGP-keyID's: 0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)
