On Sun, Mar 10, 2024 at 09:50:51PM +, Kirk McKusick wrote:
> > Date: Sun, 10 Mar 2024 19:21:54 +0200
> > From: Konstantin Belousov
> > To: Kirk McKusick
> > Cc: curr...@freebsd.org
> > Subject: Re: Reason why "nocache" option is not displayed in "mount"?
> >
> > On Sun, Mar 10, 2024 at 01:53
> Date: Sun, 10 Mar 2024 19:21:54 +0200
> From: Konstantin Belousov
> To: Kirk McKusick
> Cc: curr...@freebsd.org
> Subject: Re: Reason why "nocache" option is not displayed in "mount"?
>
> On Sun, Mar 10, 2024 at 01:53:05AM +, Kirk McKusick wrote:
>> The issue has to do with how flags are d
On Sat, Mar 09, 2024 at 04:59:49PM -0800, Rick Macklem wrote:
> Hi,
>
> I would like to compare va_size to va_bytes in vn_generic_copy_file_range(),
> as a heuristic to check for a sparse file (only works for non-compressed
> file systems).
>
> The call to VOP_GETATTR(invp, ..) was replaced by vn
On Sun, Mar 10, 2024 at 01:53:05AM +, Kirk McKusick wrote:
> The issue has to do with how flags are defined in mount.h.
> Specifically there are the flags that are externally visible
> (prefixed with MNT_) and those that are for internal use
> (prefixed with MNTK_, the K standing for KERNEL). I
