Re: Dell Latitude 7400 - nvme0: Missing interrupt

2021-10-10 Thread Warner Losh
On Sun, Oct 10, 2021 at 10:48 PM Pavel Timofeev wrote: > сб, 9 окт. 2021 г. в 14:59, Warner Losh : > >> >> >> On Sat, Oct 9, 2021, 8:44 AM Pavel Timofeev wrote: >> >>> >>> >>> пт, 8 окт. 2021 г. в 14:49, Warner Losh : >>> On Fri, Oct 8, 2021 at 2:42 PM Pavel Timofeev wrote:

Re: Dell Latitude 7400 - nvme0: Missing interrupt

2021-10-10 Thread Pavel Timofeev
сб, 9 окт. 2021 г. в 14:59, Warner Losh : > > > On Sat, Oct 9, 2021, 8:44 AM Pavel Timofeev wrote: > >> >> >> пт, 8 окт. 2021 г. в 14:49, Warner Losh : >> >>> >>> >>> On Fri, Oct 8, 2021 at 2:42 PM Pavel Timofeev wrote: >>> сб, 21 авг. 2021 г. в 15:22, Warner Losh : >

Re: clang/llvm-tblgen --- ld: error: undefined symbol: setupterm

2021-10-10 Thread Daniel Nebdal
On Sun, 10 Oct 2021 at 22:17, Baptiste Daroussin wrote: > > > > > I don't know if this is the right place to jump in, but I suspect this > > is a related issue? > > I'm trying to do the opposite - building 14 on a 13-STABLE machine. It > > fails when trying to build ncurses: > > > >

Re: clang/llvm-tblgen --- ld: error: undefined symbol: setupterm

2021-10-10 Thread Baptiste Daroussin
10 oct. 2021 16:43:52 Daniel Nebdal : > On Sun, 10 Oct 2021 at 07:46, Baptiste Daroussin wrote: >> >> On Sat, Oct 09, 2021 at 11:33:54PM -0600, Warner Losh wrote: >>> On Sat, Oct 9, 2021 at 11:29 PM Kyle Evans wrote: >>> On Sun, Oct 10, 2021 at 12:18 AM Warner Losh wrote: > > On

Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-10 Thread Willem Jan Withagen via freebsd-current
On 10-10-2021 07:57, Rick Macklem wrote: This leads me to a couple of questions: - Is there a good reason for not using vop_stdallocate() for ZFS? Yes. posix_fallocate is supposed to guarantee that subsequent writes to the file will not fail with ENOSPC. But ZFS, being a copy-on-write file

Re: clang/llvm-tblgen --- ld: error: undefined symbol: setupterm

2021-10-10 Thread Daniel Nebdal
On Sun, 10 Oct 2021 at 07:46, Baptiste Daroussin wrote: > > On Sat, Oct 09, 2021 at 11:33:54PM -0600, Warner Losh wrote: > > On Sat, Oct 9, 2021 at 11:29 PM Kyle Evans wrote: > > > > > On Sun, Oct 10, 2021 at 12:18 AM Warner Losh wrote: > > > > > > > > On Sat, Oct 9, 2021 at 10:45 PM Warner

Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-10 Thread Rick Macklem
Alan Somers wrote: [stuff snipped] >Rick Macklem wrote: > >Alan Somers wrote: > > >Yes. posix_fallocate is supposed to guarantee that subsequent writes > > >to the file will not fail with ENOSPC. But ZFS, being a copy-on-write > > >file system, cannot possibly guarantee that. See SVN r325320. >

Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-10 Thread Alan Somers
On Sat, Oct 9, 2021 at 11:57 PM Rick Macklem wrote: > > Alan Somers wrote: > >On Sat, Oct 9, 2021 at 7:13 PM Rick Macklem wrote: > >> > >> Hi, > >> > >> I ran into an issue this week during the nf...@ietf.org's testing event. > >> UFS - supports VOP_ALLOCATE() by using vop_stdallocate(). > >>

Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd

2021-10-10 Thread Warner Losh
On Sat, Oct 9, 2021, 11:58 PM Rick Macklem wrote: > Alan Somers wrote: > >On Sat, Oct 9, 2021 at 7:13 PM Rick Macklem wrote: > >> > >> Hi, > >> > >> I ran into an issue this week during the nf...@ietf.org's testing > event. > >> UFS - supports VOP_ALLOCATE() by using vop_stdallocate(). > >> ZFS