enabling inode hashes results in kernel panics

I just had two panics as a result of enabling inode hashes on a file system yesterday when I had to run fsck on it. The filesystem showed no problems at all yesterday, the problem didn't appear until I accessed it today. NOTE that my fsck was installed from r341840 yesterday morning, so it

Re: enabling inode hashes results in kernel panics

On Thu, 13 Dec 2018 10:47:13 +0100 Gary Jennejohn wrote: > I just had two panics as a result of enabling inode hashes on a > file system yesterday when I had to run fsck on it. > > The filesystem showed no problems at all yesterday, the problem > didn't appear until I accessed it today. > >

Whine: "Could not open /dev/crypto: No such file or directory"

After update from r341844 to r342042, I see the above-cited "whine" when I attempt to use an SSH client on the upgraded machine. SSH client function seems OK, so the message is (apparently) merely annoying: freebeast(13.0-C)[2] uname -a FreeBSD freebeast.catwhisker.org 13.0-CURRENT FreeBSD

src committer please

Hi, Please could somebody take a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 It’s been open for over a year with a patch that solves the problem. Failing to install out of the box on commodity HP kit is not a good look. Thanks -- Bob Bishop r...@gid.co.uk

Re: nda(4) does not work (reliably) in VMware Workstation

On Sun, Dec 9, 2018 at 3:50 PM Chuck Tuffli wrote: > On Sun, Dec 9, 2018 at 3:43 PM Yuri Pankov wrote: > >> Chuck Tuffli wrote: >> > On Sat, Dec 8, 2018 at 12:28 PM Yuri Pankov > > > wrote: >> > >> > Hi, >> > >> > Running -HEAD in VMware Workstation 15.0.2 VM.

Re: Whine: "Could not open /dev/crypto: No such file or directory"

David Wolfskill wrote: After update from r341844 to r342042, I see the above-cited "whine" when I attempt to use an SSH client on the upgraded machine. SSH client function seems OK, so the message is (apparently) merely annoying: freebeast(13.0-C)[2] uname -a FreeBSD freebeast.catwhisker.org

Re: enabling inode hashes results in kernel panics

In message <20181213113925.5f100...@ernst.home>, Gary Jennejohn writes: > On Thu, 13 Dec 2018 10:47:13 +0100 > Gary Jennejohn wrote: > > > I just had two panics as a result of enabling inode hashes on a > > file system yesterday when I had to run fsck on it. > > > > The filesystem showed no

RE: src committer please

Have you tried -CURRENT? --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -Original Message- From: Bob Bishop Sent: 13/12/2018

Re: enabling inode hashes results in kernel panics

As the person resposible for ading the inode check-hashes, sorry for the problems that they are causing you. Gary, I may want your crash dumps and the core.txt files, but let me do some preliminary investigation of fsck to see if I can figure out why it is failing to fix the inode check-hashes.

Re: Whine: "Could not open /dev/crypto: No such file or directory"

On 18. 12. 13., Yuri Pankov wrote: > David Wolfskill wrote: >> After update from r341844 to r342042, I see the above-cited "whine" when >> I attempt to use an SSH client on the upgraded machine.  SSH client >> function seems OK, so the message is (apparently) merely annoying: >> >>

Re: WITH_META_MODE: any effect? Tree built twice!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am Wed, 12 Dec 2018 16:25:56 -0800 "Simon J. Gerraty" schrieb: Hello, thanks for your resonse. > O. Hartmann wrote: > > delete-old|-libs afterwards, I started again a build (filemon loaded!). > > And, surprise, > > surprise, compilation of

Re: WITH_META_MODE: any effect? Tree built twice!

O. Hartmann wrote: > I'm able to reproduce this behaviour easily: make cleanworld; kldload filemon > (if not > already loaded); make buildworld buildkernel Why are you doing cleanworld? > After the build has finished, install everything accordingly and reboot. Then > kldload > filemon and

Re: enabling inode hashes results in kernel panics

On Thu, 13 Dec 2018 07:45:36 -0800 Cy Schubert wrote: > In message <20181213113925.5f100...@ernst.home>, Gary Jennejohn writes: > > On Thu, 13 Dec 2018 10:47:13 +0100 > > Gary Jennejohn wrote: > > > > > I just had two panics as a result of enabling inode hashes on a > > > file system

Re: src committer please

On Thursday, 13 December 2018 at 13:07:54 +, Bob Bishop wrote: > Hi, > > Please could somebody take a look at > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350 > > It???s been open for over a year with a patch that solves the problem. > > Failing to install out of the box on