Re: kern/45708: Unable to read big files from large FFSv2 (12TB), ls out of swap

[Bartosz Kuźma <bartosz.kuzma%gmail.com@localhost>]

The following reply was made to PR kern/45708; it has been noted by GNATS.

From: =?UTF-8?Q?Bartosz_Ku=C5=BAma?= <bartosz.kuzma%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/45708: Unable to read big files from large FFSv2 (12TB), ls
 out of swap
Date: Wed, 14 Dec 2011 13:44:32 +0100

 On Wed, Dec 14, 2011 at 13:40, David Holland 
<dholland-bugs%netbsd.org@localhost> wro=
 te:
 > The following reply was made to PR kern/45708; it has been noted by GNATS=
 .
 >
 > From: David Holland <dholland-bugs%netbsd.org@localhost>
 > To: gnats-bugs%NetBSD.org@localhost
 > Cc:
 > Subject: Re: kern/45708: Unable to read big files from large FFSv2 (12TB)=
 , ls
 > =C2=A0out of swap
 > Date: Wed, 14 Dec 2011 12:35:56 +0000
 >
 > =C2=A0On Tue, Dec 13, 2011 at 09:10:01AM +0000, 
 > bartosz.kuzma%gmail.com@localhost w=
 rote:
 > =C2=A0> On large filesystem (12TB) when I try to create big files I'm
 > =C2=A0> unable to ls directory.
 > =C2=A0>
 > =C2=A0> When I try to do:
 > =C2=A0>
 > =C2=A0> # ls -1 /mnt
 > =C2=A0>
 > =C2=A0> Kernel panic with the following message:
 > =C2=A0>
 > =C2=A0> UVM: pid 977 (ls), uid 0 killed: out of swap
 > =C2=A0> ubc_uiomove: error=3D12
 > =C2=A0> dev =3D 0xa800, block =3D 1305922608, fs =3D /mnt
 >
 > =C2=A0That is weird...
 >
 > =C2=A0> panic: blkfree: freeing free block
 >
 > =C2=A0...but this makes me think the real problem is that the filesystem =
 is
 > =C2=A0corrupted. Have you run fsck on it recently? Does this really happe=
 n
 > =C2=A0on a freshly newfs'd volume as described?
 >
 > =C2=A0--
 > =C2=A0David A. Holland
 > =C2=A0dholland%netbsd.org@localhost
 >
 
 Yes, it is easily reproductible on freshly newfs'd volume.
 
 When I did test with creating several large files (about 256GB each)
 and then call sync command and did unclean reboot (e. g. poweroff) it
 is unable to mount this fs again. It hangs on "replying log to disk".
 However it is possible to mount it in read-only mode. It simply put
 "replying log to memory" and works.
 
 If you need more info or even access to this machine ask me.
 
 --=20
 Pozdrawiam, Bartosz Ku=C5=BAma.