On 2018-07-19 13:18, J. Hannken-Illjes wrote:
On Thu, Jul 19, 2018 at 01:08:22PM +0200, Johnny Billquist wrote:
Hmm. That means I need to update user land, which can be a bit scary since it
can make a rollback really hard.
And there is also a chicken and egg thing here. Installing a new user
Hmm. That means I need to update user land, which can be a bit scary since it
can make a rollback really hard.
And there is also a chicken and egg thing here. Installing a new user land can
potentially mean removing files, which will trigger the panic.
Is it really motivated with that panic?
On Thu, Jul 19, 2018 at 01:08:22PM +0200, Johnny Billquist wrote:
> Hmm. That means I need to update user land, which can be a bit scary since it
> can make a rollback really hard.
> And there is also a chicken and egg thing here. Installing a new user land
> can potentially mean removing files,
> On 19. Jul 2018, at 03:54, Johnny Billquist wrote:
>
> Anyone seen this, or know what it's about?
Great, it took 6 months to trigger my assertion ...
This panic probably means the file contains unallocated inodes that
were only partially zeroed.
Please run "fsck -f" on this file system
On 2018-07-19 06:12, m...@netbsd.org wrote:
On Thu, Jul 19, 2018 at 03:54:17AM +0200, Johnny Billquist wrote:
Anyone seen this, or know what it's about?
On NetBSD/vax, with 8.99.22 from today.
Removing any file that has disk blocks allocated to it:
[ 653.3285523] ufs_inactive: unlinked ino
Hi.
On 2018-07-19 05:21, Paul Goyette wrote:
Let me update my source tree, re-build, and check.
What port are you using? i386? amd64? other?
NetBSD/vax.
A couple of more points. I upgraded the machine from 7.99.something, so
I have not run any version 8 on this machine previously. The
On Thu, Jul 19, 2018 at 03:54:17AM +0200, Johnny Billquist wrote:
> Anyone seen this, or know what it's about?
>
> On NetBSD/vax, with 8.99.22 from today.
>
> Removing any file that has disk blocks allocated to it:
>
> [ 653.3285523] ufs_inactive: unlinked ino 50313 on "/home" has non zero size
On Thu, 19 Jul 2018, Paul Goyette wrote:
Let me update my source tree, re-build, and check.
What port are you using? i386? amd64? other?
Hmmm. A -currrent from just a few minutes ago builds and runs correctly
on amd64 (using QEMU).
# dd if=/dev/zero of=test.test bs=8192 count=1k
1024+0
Let me update my source tree, re-build, and check.
What port are you using? i386? amd64? other?
On Thu, 19 Jul 2018, Johnny Billquist wrote:
Anyone seen this, or know what it's about?
On NetBSD/vax, with 8.99.22 from today.
Removing any file that has disk blocks allocated to it:
[
Anyone seen this, or know what it's about?
On NetBSD/vax, with 8.99.22 from today.
Removing any file that has disk blocks allocated to it:
[ 653.3285523] ufs_inactive: unlinked ino 50313 on "/home" has non zero
size 0 or blocks 1ac0 with allerror 0
[ 653.3484633] panic: ufs_inactive: dirty
10 matches
Mail list logo
