Date: Tue, 19 May 1998 11:14:42 -0700 (PDT) From: Julian Elischer <julian@whistle.com> To: Tom Jackson <toj@gorillanet.gorilla.net> Cc: FreeBSD Current <freebsd-current@FreeBSD.ORG> Subject: Re: devfs/slice problem Message-ID: <Pine.BSF.3.95.980519111344.20170C-100000@current1.whistle.com> In-Reply-To: <19980518231348.56058@TOJ.org>
next in thread | previous in thread | raw e-mail | index | archive | help
devfs/slice has not been ported to CAM yet.. I have mods to da.c that do SLICE stuff but I don't have a CAM system to test it on. On Mon, 18 May 1998, Tom Jackson wrote: > I found out the problem. Just after trying the new CAM snap I noticed > that procmail stopped working. I tracked that down to /dev/null being > writeable only by root; remade and it worked. Tonight noticed that > sound was no longer working; remade snd and it began working. On a hunch > remade sd1 <G>; fdisk sd1 began working. Not really sure how my device > drivers got corrupted but they did. MAKEDEV all!! > > Still there is the condition of partitions extending past end of slice, > seem to remember a warning to not disklabel etc when running devfs/slice. > Also noticed that my Syquest will not release a cartridge after it has > been mounted. Will mount and unmount, just not release it from the drive. > I guess this relates to what Julian was saying about floppy problem. On > the CAM front, running smp I was getting failures in 'make world'?? > > Happy hunting, > > On Mon, May 18, 1998 at 05:49:57PM -0500, Tom Jackson wrote: > > > > Since devfs/slice had been added to LINT I adopted it to all > > my boxes. No problem on two with single disk, dangerously > > dedicated. On the the main server box, disklabel says all disk > > end partition and 'c' partition extend past end of disk. > > > > When I tried to use sysinstall to change the slice settings on > > a brand new disk, it hung, sorry I didn't get debug messages. I > > won't go into the file system corruption I got on unrelated fs's > > ( first time ever with FreeBSD ) but the new disk now is not seen > > by /stand/sysinstall. Also fdisk can't find the slices either and > > says it is using dummy parameters 1/1/1 and then it hangs. > > > > I've got the corrupted file systems back by dumping devfs/slice > > on the server and using /stand/sysinstall to delete, bring back > > and newfs the file systems. > > > > BIG question is how do I get fdisk to work with the new disk and > > thus, let me use /stand/sysinstall to set the slice settings. The > > weird thing is msdos lets me put a dos slice on this disk, no problem, > > pfdisk shows the slices, no problem, and a boot floppy picks up the > > disk to allow me to set the slices. > > > > I'm holding off dedicating anything to this disk until I can get it > > to look normal to fdisk. > > > > Thanks for FreeBSD, > > > > > > -- > > Tom > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- > Tom > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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?Pine.BSF.3.95.980519111344.20170C-100000>