Date: Wed, 10 Apr 2019 22:51:32 -0600 From: Warner Losh <imp@bsdimp.com> To: jamie@catflap.dyslexicfish.net Cc: Peter Holm <peter@holm.cc>, jamie@catflap.org, Kirk McKusick <mckusick@mckusick.com>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: Replicable file-system corruption due to fsck/ufs Message-ID: <CANCZdfoYyatXu8Jr2RxP8xg47PWkapMrv9zdy8zs0SsLW=yOiQ@mail.gmail.com> In-Reply-To: <5caec650.75986.3515f2a1@catflap.dyslexicfish.net> References: <201904110347.x3B3lhpA034197@donotpassgo.dyslexicfish.net> <20190411043620.GA87473@x2.osted.lan> <5caec650.75986.3515f2a1@catflap.dyslexicfish.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 10, 2019 at 10:46 PM <jamie@catflap.dyslexicfish.net> wrote: > Peter Holm <peter@holm.cc> wrote: > > > I see this even with a single truncate on HEAD. > > > > $ ./truncate10.sh > > 96 -rw-r--r-- 1 root wheel 1073741824 11 apr. 06:33 test > > ** /dev/md10a > > ** Last Mounted on /mnt > > ** Phase 1 - Check Blocks and Sizes > > INODE 3: FILE SIZE 1073741824 BEYOND END OF ALLOCATED FILE, SIZE SHOULD > BE 268435456 > > ADJUST? yes > > Thanks.. I should have tested that myself.. doh! I was trying to closer > replicate > my real file that triggered the problem which contained a number of sparse > areas. > > And thanks for adding Kirk to the discussion. I wanted to first be sure it > wasn't > just me :-) > I believe that this was added recently to detect corruption that happens when a file is being appended when the system crashes. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoYyatXu8Jr2RxP8xg47PWkapMrv9zdy8zs0SsLW=yOiQ>