Date: Tue, 4 Feb 2003 18:49:24 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: phk@freebsd.org Cc: current@freebsd.org Subject: Re: Minor oddity with sysinstall/disklabel on -current Message-ID: <p05200f5dba6601734431@[128.113.24.47]> In-Reply-To: <17774.1044345863@critter.freebsd.dk> References: <17774.1044345863@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
At 9:04 AM +0100 2/4/03, phk@freebsd.org wrote: >Garance A Drosihn writes: > > 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. It occurs to me that I can now easily test this by doing a swapoff command for /dev/ad2s1b. And indeed, if I do that before the second run of sysinstall, everything works fine on the second trip through. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05200f5dba6601734431>