In message <p05200f51ba651eaf1dd8@[128.113.24.47]>, Garance A Drosihn writes: >So, I'm trying something on -current. > >I boot up, log into root. I have two hard disks on the system. All >of my mounted partitions are on ad0, except for one partition on ad2. >I 'umount' that partition. I run the Disklabel Editor via sysinstall. >I delete that partition, and then re-create it as a UFS2 partition. >I do the 'w'rite, and everything looks fine. > >I drop out of sysinstall, do some things with that partition, and >then decide to redo the above sequence. Everything has been working >fine, but I'm just testing some things and I end up in a position >where it's quicker to newfs the partition than it is to 'rm' the >files on it. So, I do the same exact sequence (starting with the >'umount' before running sysinstall), and this time when I do the >'w'rite, I am told: > > ERROR: Unable to write data to disk ad2!
My guess is that sysinstall (bogusly) did a swapon for the 'b' parititon on your ad2 disk. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
