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
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 - just return EINVAL for VOP_ALLOCATE().
>>
>> An NFSv4.2 server can e
From: Alan Somers
Sent: Saturday, October 9, 2021 11:52 PM
To: Rick Macklem
Cc: FreeBSD Current
Subject: Re: RFC: Use of VOP_ALLOCATE() by NFSV4.2 nfsd
CAUTION: This email originated from outside of the University of Guelph. Do not
click links or open a
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 Losh wrote:
> > >
> > > >
> > > >
> > > > On Sat, Oct 9, 2021 at 10:41 PM
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 Losh wrote:
> >
> > >
> > >
> > > On Sat, Oct 9, 2021 at 10:41 PM Baptiste Daroussin
> > > wrote:
> > >
> > >> On Sun, Oct 10, 2021 at 06:06:37
On Sun, Oct 10, 2021 at 12:18 AM Warner Losh wrote:
>
> On Sat, Oct 9, 2021 at 10:45 PM Warner Losh wrote:
>
> >
> >
> > On Sat, Oct 9, 2021 at 10:41 PM Baptiste Daroussin
> > wrote:
> >
> >> On Sun, Oct 10, 2021 at 06:06:37AM +0200, Baptiste Daroussin wrote:
> >> > On Sun, Oct 10, 2021 at 02:52
On Sat, Oct 9, 2021 at 10:45 PM Warner Losh wrote:
>
>
> On Sat, Oct 9, 2021 at 10:41 PM Baptiste Daroussin
> wrote:
>
>> On Sun, Oct 10, 2021 at 06:06:37AM +0200, Baptiste Daroussin wrote:
>> > On Sun, Oct 10, 2021 at 02:52:58AM +0300, Konstantin Belousov wrote:
>> > > On Sat, Oct 09, 2021 at 0
On Sat, Oct 9, 2021 at 10:41 PM Baptiste Daroussin wrote:
> On Sun, Oct 10, 2021 at 06:06:37AM +0200, Baptiste Daroussin wrote:
> > On Sun, Oct 10, 2021 at 02:52:58AM +0300, Konstantin Belousov wrote:
> > > On Sat, Oct 09, 2021 at 05:29:39PM -0600, Warner Losh wrote:
> > > > On Sat, Oct 9, 2021,
On Sat, Oct 9, 2021 at 10:06 PM Baptiste Daroussin wrote:
> On Sun, Oct 10, 2021 at 02:52:58AM +0300, Konstantin Belousov wrote:
> > On Sat, Oct 09, 2021 at 05:29:39PM -0600, Warner Losh wrote:
> > > On Sat, Oct 9, 2021, 5:15 PM Konstantin Belousov
> > > wrote:
> > >
> > > > On Sat, Oct 09, 2021
On Sun, Oct 10, 2021 at 06:06:37AM +0200, Baptiste Daroussin wrote:
> On Sun, Oct 10, 2021 at 02:52:58AM +0300, Konstantin Belousov wrote:
> > On Sat, Oct 09, 2021 at 05:29:39PM -0600, Warner Losh wrote:
> > > On Sat, Oct 9, 2021, 5:15 PM Konstantin Belousov
> > > wrote:
> > >
> > > > On Sat, Oct
On Sun, Oct 10, 2021 at 02:52:58AM +0300, Konstantin Belousov wrote:
> On Sat, Oct 09, 2021 at 05:29:39PM -0600, Warner Losh wrote:
> > On Sat, Oct 9, 2021, 5:15 PM Konstantin Belousov
> > wrote:
> >
> > > On Sat, Oct 09, 2021 at 04:47:35PM -0600, Warner Losh wrote:
> > > > On Sat, Oct 9, 2021 at
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 - just return EINVAL for VOP_ALLOCATE().
>
> An NFSv4.2 server can either support Allocate or no
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 - just return EINVAL for VOP_ALLOCATE().
An NFSv4.2 server can either support Allocate or not, but it has to be
for all exported file systems.
This leads me
On Sat, Oct 09, 2021 at 05:29:39PM -0600, Warner Losh wrote:
> On Sat, Oct 9, 2021, 5:15 PM Konstantin Belousov
> wrote:
>
> > On Sat, Oct 09, 2021 at 04:47:35PM -0600, Warner Losh wrote:
> > > On Sat, Oct 9, 2021 at 11:09 AM Dimitry Andric wrote:
> > >
> > > > On 9 Oct 2021, at 15:40, Warner Lo
On Sat, Oct 9, 2021, 5:15 PM Konstantin Belousov
wrote:
> On Sat, Oct 09, 2021 at 04:47:35PM -0600, Warner Losh wrote:
> > On Sat, Oct 9, 2021 at 11:09 AM Dimitry Andric wrote:
> >
> > > On 9 Oct 2021, at 15:40, Warner Losh wrote:
> > > >
> > > > On Sat, Oct 9, 2021, 5:59 AM Dimitry Andric wro
On Sat, Oct 09, 2021 at 04:47:35PM -0600, Warner Losh wrote:
> On Sat, Oct 9, 2021 at 11:09 AM Dimitry Andric wrote:
>
> > On 9 Oct 2021, at 15:40, Warner Losh wrote:
> > >
> > > On Sat, Oct 9, 2021, 5:59 AM Dimitry Andric wrote:
> > > On 9 Oct 2021, at 13:37, Dimitry Andric wrote:
> > > >
> >
Is the NFS mounted filesystem NFS? I've found NFS mounted ZFS has several
pathologies like this when there is no SSD cache and/or log vdevs attached.
On Wed, Oct 6, 2021 at 10:18 PM Felix Palmen wrote:
> Hi all,
>
> I use a -CURRENT bhyve vm for testing port builds with poudriere. As
> this vm
On Sat, Oct 9, 2021 at 11:09 AM Dimitry Andric wrote:
> On 9 Oct 2021, at 15:40, Warner Losh wrote:
> >
> > On Sat, Oct 9, 2021, 5:59 AM Dimitry Andric wrote:
> > On 9 Oct 2021, at 13:37, Dimitry Andric wrote:
> > >
> > > On 9 Oct 2021, at 09:46, FreeBSD User wrote:
> > >>
> > >> On recent CU
Rick Macklem wrote:
?Felix Palmen wrote:
[stuff snipped]
>>Ok, thanks for the insight here! So maybe, I could have a look at
>>poudriere's code? If I understand you correctly, keeping the file open
>>and just issuing more write() calls wouldn't trigger that problem?
>Nope, I don't think keeping the
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 :
>>>
On Sat, Aug 21, 2021 at 3:06 PM Pavel Timofeev
wro
On Fri, Oct 08, 2021 at 03:36:18PM -0400, Michael Butler wrote:
> On 10/7/21 20:19, Konstantin Belousov wrote:
> > On Thu, Oct 07, 2021 at 05:43:14PM -0400, Michael Butler wrote:
> > > On 10/7/21 16:52, Mark Johnston wrote:
> > > > On Thu, Oct 07, 2021 at 04:18:28PM -0400, Michael Butler via
> > >
On 9 Oct 2021, at 15:40, Warner Losh wrote:
>
> On Sat, Oct 9, 2021, 5:59 AM Dimitry Andric wrote:
> On 9 Oct 2021, at 13:37, Dimitry Andric wrote:
> >
> > On 9 Oct 2021, at 09:46, FreeBSD User wrote:
> >>
> >> On recent CURRENT (FreeBSD 14.0-CURRENT #2 main-n249971-0525ece3554e:
> >> Fri Oct
Felix Palmen wrote:
[stuff snipped]
>Ok, thanks for the insight here! So maybe, I could have a look at
>poudriere's code? If I understand you correctly, keeping the file open
>and just issuing more write() calls wouldn't trigger that problem?
Nope, I don't think keeping the file open would help mu
Felix Palmen wrote:
>* Rick Macklem [20211009 15:35]:
>> Felix Palmen wrote:
>> Assuming your NFS performance is acceptable for other things and it
>> is only this log file that is a problem, then I doubt there is much you
>> can do to improve it.
>
>Yes, that&
* Rick Macklem [20211009 15:35]:
> Felix Palmen wrote:
> Assuming your NFS performance is acceptable for other things and it
> is only this log file that is a problem, then I doubt there is much you
> can do to improve it.
Yes, that's the only problem I found so far…
&g
Felix Palmen wrote:
>I use a -CURRENT bhyve vm for testing port builds with poudriere. As
>this vm is only running when needed, but I want to always have access to
>the build logs, I use NFS to mount /usr/local/poudriere/data/logs from
>the host.
>
>I noticed some few ports take ridiculously long t
пт, 8 окт. 2021 г. в 14:49, Warner Losh :
>
>
> On Fri, Oct 8, 2021 at 2:42 PM Pavel Timofeev wrote:
>
>>
>>
>> сб, 21 авг. 2021 г. в 15:22, Warner Losh :
>>
>>>
>>>
>>> On Sat, Aug 21, 2021 at 3:06 PM Pavel Timofeev wrote:
>>>
Warner Losh :
>
>
> On Fri, Aug 20,
* Mehmet Erol Sanliturk [20211007 10:42]:
> The problem is caused mainly by NFS definition parameters .
>
> If you study NFS definition parameters one by one , I think you will be
> able to find which one is effective .
>
> My opinion is the one setting is "write directly to disk" , i.e. , "do
On Sat, Oct 9, 2021, 5:59 AM Dimitry Andric wrote:
> On 9 Oct 2021, at 13:37, Dimitry Andric wrote:
> >
> > On 9 Oct 2021, at 09:46, FreeBSD User wrote:
> >>
> >> On recent CURRENT (FreeBSD 14.0-CURRENT #2 main-n249971-0525ece3554e:
> >> Fri Oct 8 15:17:34 CEST 2021 amd64) building of an 13-ST
On Thu, 23 Sep 2021, Hans Ottevanger wrote:
[snip]
> While there, you could change "Charlie &" in the gecos field to something more
> sensible, e.g. just "Superuser". I know Charlie is there since 4.2BSD, but the
> reference to a long forgotten baseball player is probably lost by now. Also, a
> l
On 9 Oct 2021, at 13:37, Dimitry Andric wrote:
>
> On 9 Oct 2021, at 09:46, FreeBSD User wrote:
>>
>> On recent CURRENT (FreeBSD 14.0-CURRENT #2 main-n249971-0525ece3554e:
>> Fri Oct 8 15:17:34 CEST 2021 amd64) building of an 13-STABLE based
>> appliance failed very early in the build process
On 9 Oct 2021, at 09:46, FreeBSD User wrote:
>
> On recent CURRENT (FreeBSD 14.0-CURRENT #2 main-n249971-0525ece3554e:
> Fri Oct 8 15:17:34 CEST 2021 amd64) building of an 13-STABLE based
> appliance failed very early in the build process of the 13-STABLE
> sources as shown below. 13-STABLE is m
On Sat, Oct 9, 2021 at 9:48 AM FreeBSD User wrote:
> On recent CURRENT (FreeBSD 14.0-CURRENT #2 main-n249971-0525ece3554e:
> Fri Oct 8 15:17:34 CEST 2021 amd64) building of an 13-STABLE based
> appliance failed very early in the build process of the 13-STABLE
> sources as shown below. 13-STABLE
On recent CURRENT (FreeBSD 14.0-CURRENT #2 main-n249971-0525ece3554e:
Fri Oct 8 15:17:34 CEST 2021 amd64) building of an 13-STABLE based
appliance failed very early in the build process of the 13-STABLE
sources as shown below. 13-STABLE is most recent, since the sources are
fetched every time the
34 matches
Mail list logo
