Date: Fri, 18 May 2001 19:14:25 -0500 From: Mike Meyer <mwm@mired.org> To: Erik Trulsson <ertr1013@student.uu.se> Cc: questions@freebsd.org, vcardona@home.com Subject: Re: disk partition / label Message-ID: <15109.47841.547550.215410@guru.mired.org> In-Reply-To: <81427530@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Erik Trulsson <ertr1013@student.uu.se> types: > On Fri, May 18, 2001 at 09:10:24AM -0600, Mike Oligny wrote: > > I have several IDE disks in a 4.3 machine: > > > > Filesystem Size Used Avail Capacity Mounted on > > /dev/ad0s1a 97M 78M 11M 87% / > > /dev/ad0s1f 18G 396M 16G 2% /usr > > /dev/ad0s1e 19M 2.7M 15M 15% /var > > procfs 4.0K 4.0K 0B 100% /proc > > /dev/ad2s1 55G 19G 32G 37% /usr2 > > /dev/ad3s1 28G 15G 11G 57% /usr3 > > /dev/ad4s1 55G 39G 12G 77% /usr4 > > /dev/ad5s1e 74G 39G 30G 57% /usr5 > > /dev/ad6s1 74G 29G 39G 43% /usr6 > > /dev/ad7s1e 74G 1.0K 68G 0% /usr7 > > Anyone know why two of them have the 'e' at the end? Perhaps I didn't > > look hard enough, but I have been unable to figure out what I did > > differently when creating these.. only thing I can think of is I > > created 5 & 7 after compiling the kernel myself, and the rest with a > > generic kernel. > My question would rather be why you *don't* have an 'e' at the end of > the others? > My guess would be that the disks without the 'e' are using a > 'dangerously dedicated' partition unlike the others. Possibly half-right. Dangerously dedicated disks don't have slices, as indicated by the s1 in the disks, but you can use the sliced device names on them. I recommend not doing that so you can recognized DD devices by the name, as I'm not sure how to decide if a disk is DD after the fact. However, he may have created some of the disks as DD and gotten a different default disklabel by doing so. He's getting a partition that starts at offset 0. I suspect he's getting either the a or c partition for those; checking the device numbers (file works nicely for that) on /dev/ad2s1, /dev/ad2s1a and /dev/ad2s1c should reveal which is the case. I'd recommend changing the entries in fstab to match reality, and possibly editing /etc/dumpdates if you're using that as well. > > I would ignore it, but I am having some weird problems with ad5s1e -- > > hard write errors? Sounds bad. :) > It is quite unlikely that this is the reason behind any problems you > are having though. Yup, it certainly is unlikely. Given the size of ad5, it's a relatively new disk. I'd move the data off and take advantage of the manufacturers warranty, as it seems to be faililng. <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15109.47841.547550.215410>