[EMAIL PROTECTED] wrote: > Quoting Otto Moerbeek <[EMAIL PROTECTED]>: > >> >> On Wed, 31 Jan 2007, Tony Abernethy wrote: >> >>> [EMAIL PROTECTED] wrote: >>> 16 partitions: >>> # size offset fstype [fsize bsize cpg] >>> a: 390721968 0 4.2BSD 2048 16384 328 # Cyl 0 >>> -387620 >>> c: 390721968 0 unused 0 0 # Cyl 0 >>> -387620 >>> >>> Most likely, the disklabel or boot code >>> or whatever occupies the initial sector(s) >>> is being interpreted as disk usage by the partition. >>> >>> Start the partition 1 cylinder in from the beginning. >> >> See http://www.openbsd.org/faq/faq4.html#blankfdisk >> >> On i386 and amd4, always use fdisk -i on a new disk before creating the >> disklabel. If you do that, disklabel will do the right thing >> automatically. > > We have a winner here! :-) > > I realized after running 'fdisk -i wd1' and then 'disklabel -E wd1' that > my previous use of disklabel had the partition starting at offset 0, not > offset 63 as expected. After recreating the disklabel this way and > re-running newfs, I get a much happier result: > > -bash-3.1$ df -h > Filesystem Size Used Avail Capacity Mounted on > /dev/wd0a 7.3G 79.1M 6.9G 1% / > /dev/wd0d 22.0G 512M 20.4G 2% /usr > /dev/wd0e 7.2G 6.8M 6.8G 0% /var > /dev/wd1a 183G 2.0K 174G 0% /mnt > > ...though to be honest I would have *never* figured that out based on > the above-mentioned FAQ entry. Would it make sense if I wrote an > addition to the entry giving this sort of scenario as an example, or is > that overkill? > > Alex
Not so much overkill, but a very specific manifestation of a general problem. While I wouldn't object to seeing what you propose, there are many problems where the problem experiencer just has to provide a lot of information and the trouble shooters have to look at it ALL and look or things that are wrong or odd, and then ask themselves, "Could this be what the problem is?". Not every question posted on misc@ can be answered by a simple RTFM... :) A curious thing about this is I believe it is possible to successfully run the system as you built it, though it is HIGHLY advised against, as they are very fragile configurations. A number of events could cause you to lose all your data...or in your case, "funny stuff to happen" (though I suspect if you had a lot of data on there, you'd be unhappy at the moment). Nick.
