FreeBSD source tree https://cgit-dev.freebsd.org/src-test/atom?h=main 2020-10-25T01:36:33Z 2020-10-25T01:36:33Z Kirk McKusick mckusick@FreeBSD.org 2020-10-25T01:36:33Z urn:sha1:6eb925f8450ffbb849195f26e26bfd4eadbcfb1d and fsirand(8)) should check the filesystem status and require that fsck(8) be run if it is unclean. This requirement is not imposed on fsdb(8) or clri(8) since they may be used to clean up a filesystem. MFC after: 2 weeks Sponsored by: Netflix 2020-09-22T03:57:48Z Kirk McKusick mckusick@FreeBSD.org 2020-09-22T03:57:48Z urn:sha1:54fab0fbc4a03fcf430cd8e8184e1196c53daf2e of filesystems. Reported by: Colin Percival (cperciva@) Tested by: Colin Percival (cperciva@) MFC after: 3 days Sponsored by: Netflix 2018-12-06T00:09:39Z Kirk McKusick mckusick@FreeBSD.org 2018-12-06T00:09:39Z urn:sha1:fb14e73cb4062d7272ce6183d748adedd868906b superblock has a check-hash error, an error message noting the superblock check-hash failure is printed and the mount fails. The administrator then runs fsck to repair the filesystem and when successful, the filesystem can once again be mounted. This approach fails if the filesystem in question is a root filesystem from which you are trying to boot. Here, the loader fails when trying to access the filesystem to get the kernel to boot. So it is necessary to allow the loader to ignore the superblock check-hash error and make a best effort to read the kernel. The filesystem may be suffiently corrupted that the read attempt fails, but there is no harm in trying since the loader makes no attempt to write to the filesystem. Once the kernel is loaded and starts to run, it attempts to mount its root filesystem. Once again, failure means that it breaks to its prompt to ask where to get its root filesystem. Unless you have an alternate root filesystem, you are stuck. Since the root filesystem is initially mounted read-only, it is safe to make an attempt to mount the root filesystem with the failed superblock check-hash. Thus, when asked to mount a root filesystem with a failed superblock check-hash, the kernel prints a warning message that the root filesystem superblock check-hash needs repair, but notes that it is ignoring the error and proceeding. It does mark the filesystem as needing an fsck which prevents it from being enabled for writing until fsck has been run on it. The net effect is that the reboot fails to single user, but at least at that point the administrator has the tools at hand to fix the problem. Reported by: Rick Macklem (rmacklem@) Discussed with: Warner Losh (imp@) Sponsored by: Netflix 2018-11-13T21:40:56Z Kirk McKusick mckusick@FreeBSD.org 2018-11-13T21:40:56Z urn:sha1:9fc5d538fc57f438ca860e07db191b946b4768c9 document the libufs interface for fetching and storing inodes. The undocumented getino / putino interface has been replaced with a new getinode / putinode interface. Convert the utilities that had been using the undocumented interface to use the new documented interface. No functional change (as for now the libufs library does not do inode check-hashes). Reviewed by: kib Tested by: Peter Holm Sponsored by: Netflix 2018-01-26T00:58:32Z Kirk McKusick mckusick@FreeBSD.org 2018-01-26T00:58:32Z urn:sha1:dffce2150eeac1c7f424324a5cade7a97b308979 Specifically reading is done if ffs_sbget() and writing is done in ffs_sbput(). These functions are exported to libufs via the sbget() and sbput() functions which then used in the various filesystem utilities. This work is in preparation for adding subperblock check hashes. No functional change intended. Reviewed by: kib 2017-12-13T14:08:33Z Edward Tomasz Napierala trasz@FreeBSD.org 2017-12-13T14:08:33Z urn:sha1:b8ea5b468b5cc52fa26a0e242d30f5736d3b6821 MFC after: 2 weeks 2017-11-18T14:26:50Z Pedro F. Giffuni pfg@FreeBSD.org 2017-11-18T14:26:50Z urn:sha1:df57947f083046d50552e99b91074927d2458708 The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts. Special thanks to Wind River for providing access to "The Duke of Highlander" tool: an older (2014) run over FreeBSD tree was useful as a starting point. Initially, only tag files that use BSD 4-Clause "Original" license. RelNotes: yes Differential Revision: https://reviews.freebsd.org/D13133 2017-10-31T00:07:04Z Bryan Drewery bdrewery@FreeBSD.org 2017-10-31T00:07:04Z urn:sha1:ea825d02749f382c3f7e17f28247f20a48733eab Sponsored by: Dell EMC Isilon 2017-10-10T21:16:07Z Ed Maste emaste@FreeBSD.org 2017-10-10T21:16:07Z urn:sha1:4887fa36354b4cdb0609d960bc1bc63d5bc68125 The build was broken on GCC-using architectures with: growfs.c: In function 'cgckhash': growfs.c:1753: warning: old-style function definition Sponsored by: The FreeBSD Foundation 2017-10-10T16:17:03Z Kirk McKusick mckusick@FreeBSD.org 2017-10-10T16:17:03Z urn:sha1:3abf5d76f2edee77981540feac63b2c0edfdbed7 This makes the needed changes to add/update cylinder group check hashes when a filesystem is expanded. Reported by: kib and Warner Losh (imp) Reviewed by: kib Tested by: Peter Holm (pho)