On Tue, 5 Jun 2007, Emilio Perea wrote:
> On Tue, Jun 05, 2007 at 07:51:48AM +0200, Otto Moerbeek wrote:
> > There were some validations checkc added to partitions. If a bad
> > partition is found, it will be marked "unused". The checks were a
> > little to strict for some cases. A fix for that went in yesterday, so
> > try a new snap.
> >
> > If the problem persists, please report with full disklabel output.
>
> The problem showed up on the latest snapshot as of now, which may well
> have been built before the fix you mention was incorporated. The home
> PC running -current has not had a problem since Saturday afternoon.
>
> The daily insecurity reports show four changes in this partition during
> the last couple of months. (Note that since this is on /usr/obj on a PC
> running -current, newfs is run just about every day.) It seems "funny"
> that on May 29 the fsize and bsize were changed to 0, but nothing weird
> happened until the day after they were changed to what appeared to be
> more reasonable numbers.
>
> Anyhow, in case the information is useful, the insecurity messages and
> current disklabel follow:
>
> ======
> sd0 diffs (-OLD +NEW)
> ======
> --- /var/backups/disklabel.sd0.current Fri Apr 21 01:31:35 2006
> +++ /var/backups/disklabel.sd0 Tue Apr 17 01:31:10 2007
> @@ -26,4 +26,4 @@
> d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 -
> 1647
> e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 -
> 2059
> f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 -
> 5356
> - g: 4139682 13628208 4.2BSD 2048 16384 480 # Cyl 5357 -
> 6984*
> + g: 4139682 13628208 4.2BSD 2048 16384 1 # Cyl 5357 -
> 6984*
The cpg change is due to making newfs "cylinder unaware".
.
>
> ======
> sd0 diffs (-OLD +NEW)
> ======
> --- /var/backups/disklabel.sd0.current Tue Apr 17 01:31:10 2007
> +++ /var/backups/disklabel.sd0 Wed May 30 01:32:08 2007
> @@ -26,4 +26,4 @@
> d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 -
> 1647
> e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 -
> 2059
> f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 -
> 5356
> - g: 4139682 13628208 4.2BSD 2048 16384 1 # Cyl 5357 -
> 6984*
> + g: 4139682 13628208 4.2BSD 0 0 1 # Cyl 5357 -
> 6984*
Here you are running with a new kernel, but userland is still old.
Hense the 0 fsize and bsize
> ======
> sd0 diffs (-OLD +NEW)
> ======
> --- /var/backups/disklabel.sd0.current Wed May 30 01:32:08 2007
> +++ /var/backups/disklabel.sd0 Fri Jun 1 01:32:15 2007
> @@ -26,4 +26,4 @@
> d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 -
> 1647
> e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 -
> 2059
> f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 -
> 5356
> - g: 4139682 13628208 4.2BSD 0 0 1 # Cyl 5357 -
> 6984*
> + g: 4139682 13628208 4.2BSD 2048 8192 1 # Cyl 5357 -
> 6984*
newfs is run, but it is still using the old struct partition format.
Hence the wrong fsize anf bsize.
>
> ======
> sd0 diffs (-OLD +NEW)
> ======
> --- /var/backups/disklabel.sd0.current Fri Jun 1 01:32:15 2007
> +++ /var/backups/disklabel.sd0 Tue Jun 5 01:32:10 2007
> @@ -26,4 +26,4 @@
> d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 -
> 1647
> e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 -
> 2059
> f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 -
> 5356
> - g: 4139682 13628208 4.2BSD 2048 8192 1 # Cyl 5357 -
> 6984*
> + g: 4139682 13628208 4.2BSD 2048 16384 1 # Cyl 5357 -
> 6984*
And here things are back in shape.
>
>
> # Inside MBR partition 3: type A6 start 63 size 17767827
> # /dev/rsd0c:
> type: SCSI
> disk: SCSI disk
> label: ST39102LW
> flags:
> bytes/sector: 512
> sectors/track: 212
> tracks/cylinder: 12
> sectors/cylinder: 2544
> cylinders: 6962
> total sectors: 17783240
> rpm: 3600
> interleave: 1
> trackskew: 0
> cylinderskew: 0
> headswitch: 0 # microseconds
> track-to-track seek: 0 # microseconds
> drivedata: 0
>
> 16 partitions:
> # size offset fstype [fsize bsize cpg]
> a: 2096193 63 4.2BSD 2048 16384 480 # Cyl 0*- 823
> b: 1048128 2096256 swap # Cyl 824 - 1235
> c: 17783240 0 unused 0 0 # Cyl 0 -
> 6990*
> d: 1048128 3144384 4.2BSD 2048 16384 416 # Cyl 1236 - 1647
> e: 1048128 4192512 4.2BSD 2048 16384 416 # Cyl 1648 - 2059
> f: 8387568 5240640 4.2BSD 2048 16384 480 # Cyl 2060 - 5356
> g: 4139682 13628208 4.2BSD 2048 16384 1 # Cyl 5357 -
> 6984*
>
We have seen some reports now on disappearing paritions. On sparc and
sparc64, there were actual bugs that have been fixed now.
For all platforms, the suspect new consistency checking code now been
disabled until we find out what is causing the mishap, and (very)
recent kernels should be back to normal.
Please report with dikslabel info and dmesg if things are still going
wrong. Preferable with fdisk (if applicable) and old disklabel
information as well.
-Otto
