On Sun, Nov 18, 2018 at 09:37:53AM +0100, Otto Moerbeek wrote:
> On Sat, Nov 17, 2018 at 07:55:33PM -0500, R. Clayton wrote:
>
> > I'm on this
> >
> > # uname -a
> > OpenBSD AngkorWat.rclayton.net 6.4 GENERIC.MP#364 amd64
> >
> > #
> >
> > and I'm trying to write some file systems on this
> >
> > # disklabel -p g sd1
> > # /dev/rsd1c:
> > type: SCSI
> > disk: SCSI disk
> > label: Rugged FW USB3
> > duid: 7e82b7f3472419e3
> > flags:
> > bytes/sector: 512
> > sectors/track: 63
> > tracks/cylinder: 255
> > sectors/cylinder: 16065
> > cylinders: 243201
> > total sectors: 3907029168 # total bytes: 1863.0G
> > boundstart: 0
> ^
> You didn't run fdisk -i on the disk, right?
>
> -Otto
Some more explanation:
After a successful run, newfs writes some meta-info to the disklabel.
This information is used in case of damage to the superblock to find
alternate superbocks. If you do not run fdisk -i before labelling on a
arch that requires it, the updating of the label fails and you will
miss some info needed by fsck in case of disk trouble.
-Otto
