Re: I replicated "UFS2 superblock failed: fs->fs_csaddr (805328) != cgdmin(fs, 0) (5048)" style failure via main 9aa02d5120a (June 30, via snapshot)
Mark Millard <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm,gmane.os.freebsd.current |
|---|---|
| Message-ID | <[email protected]> |
On 2022-Jul-5, at 18:19, Mark Millard <[email protected]> wrote: > On 2022-Jul-5, at 15:59, Mark Millard <[email protected]> wrote: > >> I did a: >> >> # dd if=FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20220701-9aa02d5120a-256480.img of=/dev/da0 bs=1m conv=sync status=progress >> 3113222144 bytes (3113 MB, 2969 MiB) transferred 13.064s, 238 MB/s >> 3072+0 records in >> 3072+0 records out >> >> to an around 1 TiByte USB3 NVMe based drive: >> >> 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 = 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=0x2<NO_6_BYTE> >> >> On booting via the media the growfs happened but at its end was: >> >> . . . >> 1947561600, 1948842048, 1950122496, 1951402944, 1952683392 >> UFS2 superblock failed: fs->fs_csaddr (805328) != cgdmin(fs, 0) (5048) >> UFS2 superblock failed: fs->fs_csaddr (805328) != cgdmin(fs, 0) (5048) >> Mounting local filesystems:. >> . . . >> >> Unfortunately, >> >> Thu, 30 Jun 2022 >> • git: 9aa02d5120ab - main - vmm: Fix snapshots for AMD CPUs John Baldwin >> >> is from after: >> >> Tue, 28 Jun 2022 >> • git: 2049cc321815 - main - Correctly update fs_dsize in growfs(8) Kirk McKusick >> >> so there still is some form of error in the growfs >> activity. >> >> At least there is now a known, specific way to produce the >> problem >> > > I tried different, smaller media: > > 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 = 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=0x2<NO_6_BYTE> > > I still got the problem. > 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. === Mark Millard marklmi at yahoo.com