> On 4. Jan 2018, at 12:14, O. Hartmann <ohartmann_at_walstatt.org> wrote: > > On Thu, 4 Jan 2018 09:10:37 +0100 > Michael Tuexen <tuexen_at_freebsd.org> wrote: > >>> On 31. Dec 2017, at 02:45, Warner Losh <imp_at_bsdimp.com> wrote: >>> >>> On Sat, Dec 30, 2017 at 4:41 PM, O. Hartmann <ohartmann_at_walstatt.org> wrote: >>> >>>> On most recent CURRENT I face the error shwon below on /tmp filesystem >>>> (UFS2) residing >>>> on a Samsung 850 Pro SSD: >>>> >>>> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3 != >>>> bp: 0xd9fba319 >>>> handle_workitem_freefile: got error 5 while accessing filesystem >>>> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3 >>>> != bp: 0xd9fba319 >>>> handle_workitem_freefile: got error 5 while accessing filesystem >>>> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3 >>>> != bp: 0xd9fba319 >>>> handle_workitem_freefile: got error 5 while accessing filesystem >>>> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3 >>>> != bp: 0xd9fba319 >>>> handle_workitem_freefile: got error 5 while accessing filesystem >>>> UFS /dev/gpt/tmp (/tmp) cylinder checksum failed: cg 0, cgp: 0x4515d2a3 >>>> != bp: 0xd9fba319 >>>> handle_workitem_freefile: got error 5 while accessing filesystem >>>> >>>> I've already formatted the /tmp filesystem, but obviously without any >>>> success. >>>> >>>> Since I face such strange errors also on NanoBSD images dd'ed to SD cards, >>>> I guess there >>>> is something fishy ... >>> >>> >>> It indicates a problem. We've seen these 'corruptions' on data in motion at >>> work, but I hacked fsck to report checksum mismatches (it silently corrects >>> them today) and we've not seen any mismatch when we unmount and fsck the >>> filesystem. >> Not sure this helps: But we have seen this also after system panics >> when having soft update journaling enabled. Having soft update journaling >> disabled, we do not observed this after several panics. >> Just to be clear: The panics are not related to this issue, >> but to other network development we do. >> >> You can check using tunefs -p devname if soft update journaling is enabled or >> not. > > In all cases I reported in earlier and now, softupdates ARE ENABLED on all > partitions in question (always GPT, in my cases also all on flash based > devices, SD card and/or SSD). OK. That seems to be consistent. Here is the config I'm using on m-SATA SSDs and I'm NOT experiencing the problem: tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) disabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) enabled tunefs: maximum blocks per file in a cylinder group: (-e) 4096 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: space to hold for metadata blocks: (-k) 6408 tunefs: optimization preference: (-o) time tunefs: volume label: (-L) This was the config I was experiencing the problem: tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) enabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) enabled tunefs: maximum blocks per file in a cylinder group: (-e) 4096 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: space to hold for metadata blocks: (-k) 6408 tunefs: optimization preference: (-o) time tunefs: volume label: (-L) So "soft updates" are enabled on both configs, but "soft update journaling" is different. Maybe this helps in nailing down the problem. Best regards Michael > >> >> Best regards >> Michael >>> >>> Warner >>> _______________________________________________ >>> freebsd-current_at_freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >> >> _______________________________________________ >> freebsd-current_at_freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org" >Received on Thu Jan 04 2018 - 17:52:34 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:14 UTC