Kirk McKusick wrote:
> > From: Peter Holm
> >
> > On Fri, Apr 12, 2019 at 04:13:00PM -0700, Kirk McKusick wrote:
> >
> >> This is indeed a bug in the calculation of the location of the last
> >> block of a file. I believe that the following patch to head will
> >> fix it.
> >>
> >> Peter, can
> Date: Sat, 13 Apr 2019 14:32:45 +0200
> From: Peter Holm
> To: Kirk McKusick
> Cc: Jamie Landeg-Jones , ja...@catflap.dyslexicfish.net,
> Warner Losh , freebsd-stable@freebsd.org
> Subject: Re: Replicable file-system corruption due to fsck/ufs
>
> On Fri, Ap
On Fri, Apr 12, 2019 at 04:13:00PM -0700, Kirk McKusick wrote:
> > Peter Holm 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
> Peter Holm 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 ALLOCAT
On Wed, Apr 10, 2019 at 10:46 PM wrote:
> Peter Holm 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
> > IN
Peter Holm 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, SIZ
On Thu, Apr 11, 2019 at 04:47:43AM +0100, Jamie Landeg-Jones wrote:
> I've noticed a replicable disk corruption by fsck_ufs/ffs on sparse files.
>
> This is on amd/64 12-stable-20190409, but I first noticed it on
> 12-stable-20190326.
>
> I didn't notice it on my previous build of 12-stable-20190
I've noticed a replicable disk corruption by fsck_ufs/ffs on sparse files.
This is on amd/64 12-stable-20190409, but I first noticed it on
12-stable-20190326.
I didn't notice it on my previous build of 12-stable-20190107, but I
may not have had any relevant sparse files at the time, so I don't kn
