Date: Tue, 5 Jul 2022 18:24:12 -0700 From: Mark Millard <marklmi@yahoo.com> To: "mckusick@freebsd.org" <mckusick@FreeBSD.org> Cc: bob prohaska <fbsd@www.zefox.net>, "freebsd-arm@freebsd.org" <arm@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: I replicated "UFS2 superblock failed: fs->fs_csaddr (805328) != cgdmin(fs, 0) (5048)" style failure via main 9aa02d5120a (June 30, via snapshot) Message-ID: <B1990B68-762A-4FF1-8130-A2E63B8083F3@yahoo.com> In-Reply-To: <562119CC-B142-493F-A7DF-F756A43F5358@yahoo.com> References: <859EFD2F-61CD-4A9D-8798-78FEAC7AAEF8.ref@yahoo.com> <859EFD2F-61CD-4A9D-8798-78FEAC7AAEF8@yahoo.com> <562119CC-B142-493F-A7DF-F756A43F5358@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2022-Jul-5, at 18:19, Mark Millard <marklmi@yahoo.com> wrote: > On 2022-Jul-5, at 15:59, Mark Millard <marklmi@yahoo.com> wrote: >=20 >> I did a: >>=20 >> # dd = if=3DFreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20220701-9aa02d5120a-256480.im= g of=3D/dev/da0 bs=3D1m conv=3Dsync status=3Dprogress >> 3113222144 bytes (3113 MB, 2969 MiB) transferred 13.064s, 238 MB/s >> 3072+0 records in >> 3072+0 records out >>=20 >> to an around 1 TiByte USB3 NVMe based drive: >>=20 >> usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage = device Samsung PSSD T7 Touch (0x04e8:0x4001) >> ugen1.5: <Samsung PSSD T7 Touch> at usbus1 >> umass0 on uhub4 >> umass0: <Samsung PSSD T7 Touch, class 0/0, rev 3.20/1.00, addr 21> on = usbus1 >> umass0: SCSI over Bulk-Only; quirks =3D 0x0100 >> umass0:6:0: Attached to scbus6 >> da0 at umass-sim0 bus 0 scbus6 target 0 lun 0 >> da0: <Samsung PSSD T7 Touch 0> Fixed Direct Access SPC-4 SCSI device >> da0: Serial Number REDACTED >> da0: 400.000MB/s transfers >> da0: 953869MB (1953525168 512 byte sectors) >> da0: quirks=3D0x2<NO_6_BYTE> >>=20 >> On booting via the media the growfs happened but at its end was: >>=20 >> . . . >> 1947561600, 1948842048, 1950122496, 1951402944, 1952683392 >> UFS2 superblock failed: fs->fs_csaddr (805328) !=3D cgdmin(fs, 0) = (5048) >> UFS2 superblock failed: fs->fs_csaddr (805328) !=3D cgdmin(fs, 0) = (5048) >> Mounting local filesystems:. >> . . . >>=20 >> Unfortunately, >>=20 >> Thu, 30 Jun 2022 >> =E2=80=A2 git: 9aa02d5120ab - main - vmm: Fix snapshots for AMD = CPUs John Baldwin >>=20 >> is from after: >>=20 >> Tue, 28 Jun 2022 >> =E2=80=A2 git: 2049cc321815 - main - Correctly update fs_dsize = in growfs(8) Kirk McKusick >>=20 >> so there still is some form of error in the growfs >> activity. >>=20 >> At least there is now a known, specific way to produce the >> problem >>=20 >=20 > I tried different, smaller media: >=20 > usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage = device OWC Envoy Pro mini (0x1e91:0xa2a5) > ugen1.5: <OWC Envoy Pro mini> at usbus1 > umass0 on uhub4 > umass0: <OWC Envoy Pro mini, class 0/0, rev 3.00/1.00, addr 25> on = usbus1 > umass0: SCSI over Bulk-Only; quirks =3D 0x0100 > umass0:6:0: Attached to scbus6 > da0 at umass-sim0 bus 0 scbus6 target 0 lun 0 > da0: <OWC Envoy Pro mini 0> Fixed Direct Access SPC-4 SCSI device > da0: Serial Number REDACTED > da0: 400.000MB/s transfers > da0: 228936MB (468862128 512 byte sectors) > da0: quirks=3D0x2<NO_6_BYTE> >=20 > I still got the problem. >=20 But the context was 13.1-RELEASE for this smaller media, instead of main, so the context predates the growfs change recently made in main [so: 14]. Thus, the details matter for if this newer failure was expected or not. I do not know. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B1990B68-762A-4FF1-8130-A2E63B8083F3>