On Thu, May 13, 2021 at 5:02 PM Rick Macklem wrote:
> Hi,
>
> I believe that NFSv4.1 and NFSv4.2 are now mature in freebsd-current/main.
> I also believe that NFSv4.1/4.2 is a better protocol than NFSv4.0.
> (In particular, the sessions mechanism for "exactly once RPC semantics"
> is a significa
That man page is getting pretty big. However, it's not always obvious
which section a particular setting should be in. Right now, you can always
just search through the entire thing. But searching would be harder if it
were split up. So I vote to keep it together.
-Alan
On Mon, May 24, 2021 at
Strangers are submitting pull requests to our Github mirror, but we rarely
pay attention. I just added a .github/CODEOWNERS file to our repo to
automatically assign reviewers to PRs. I based it off of the contents of
the current MAINTAINERS file. But it's incomplete. Please add yourself if:
*
On Thu, Jun 3, 2021 at 8:13 PM Rick Macklem wrote:
> Hi,
>
> I am trying to MFC a commit to stable/12.
> The cherry-pick works, but the resultant code
> is not correct and won't build.
> --> I broke the build yesterday and manually
>reverted the breakage.
>
> So, how do I do this?
>
> Do
FreeBSD has always placed /usr/local/X after /usr/X in the default PATH.
AFAICT that convention began with SVN revision 37 "Initial import of 386BSD
0.1 othersrc/etc". Why is that? It would make sense to me that
/usr/local/X should come first. That way programs installed from ports can
override
On Fri, Jul 16, 2021 at 9:54 AM Cameron Katri via freebsd-current <
freebsd-current@freebsd.org> wrote:
> On Fri, Jul 16, 2021 at 09:01:49AM -0600, Alan Somers wrote:
> > FreeBSD has always placed /usr/local/X after /usr/X in the default PATH.
> > AFAICT that convention began
On Fri, Jul 16, 2021 at 10:46 AM Ian Lepore wrote:
> On Fri, 2021-07-16 at 09:01 -0600, Alan Somers wrote:
> > FreeBSD has always placed /usr/local/X after /usr/X in the default PATH.
> > AFAICT that convention began with SVN revision 37 "Initial import of
> 386BSD
> &g
Is it possible to build multiple different kernels and include them all in
a release image? release.conf says so. But from experiment, what I see is
that:
* release.sh does pass both kernels in the KERNCONF variable to "make
buildkernel"
* "make buildkernel" dutifully builds both
* BUT, "make in
On Wed, Jul 28, 2021 at 11:28 AM Glen Barber wrote:
> On Wed, Jul 28, 2021 at 05:26:50PM +, Glen Barber wrote:
> > On Wed, Jul 28, 2021 at 11:11:48AM -0600, Alan Somers wrote:
> > > Is it possible to build multiple different kernels and include them
> all in
On Wed, Jul 28, 2021 at 11:57 AM Glen Barber wrote:
> On Wed, Jul 28, 2021 at 05:32:03PM +, Glen Barber wrote:
> > On Wed, Jul 28, 2021 at 11:30:44AM -0600, Alan Somers wrote:
> > > On Wed, Jul 28, 2021 at 11:28 AM Glen Barber wrote:
> > >
> > > > O
On Wed, Jul 28, 2021 at 5:52 PM Miroslav Lachman <000.f...@quip.cz> wrote:
> On 28/07/2021 20:46, Juraj Lutter wrote:
> >
> >
> >> On 28 Jul 2021, at 20:37, Glen Barber wrote:
> >>
> >> On Wed, Jul 28, 2021 at 12:05:25PM -0600, Alan Somers wr
I don't know of any way to do it using the official release scripts either.
One problem is that every ZFS pool and file system is supposed to have a
unique GUID. So any kind of ZFS release builder would need to re-guid the
pool on first boot.
On Thu, Aug 5, 2021, 6:41 AM David Chisnall wrote:
>
There's this:
https://openzfs.github.io/openzfs-docs/man/8/zpool-reguid.8.html . I
haven't used it myself.
On Thu, Aug 5, 2021, 9:29 AM David Chisnall wrote:
> On 05/08/2021 13:53, Alan Somers wrote:
> > I don't know of any way to do it using the official release
On Thu, Jul 29, 2021 at 12:43 PM Emmanuel Vadot
wrote:
> On Thu, 29 Jul 2021 00:13:54 +
> Glen Barber wrote:
>
> > On Wed, Jul 28, 2021 at 06:00:28PM -0600, Alan Somers wrote:
> > > On Wed, Jul 28, 2021 at 5:52 PM Miroslav Lachman <000.f...@quip.cz>
> wrot
We usually try to maintain backwards compatibility forever. But is that
necessary for the ses(4) ioctls? There are several problems with them as
currently defined. They lack type safety, lack automatic copyin/copyout
handling, and one of them can overrun a user buffer. I would like to fix
them,
On Thu, Aug 26, 2021 at 2:21 AM David Chisnall wrote:
> On 25/08/2021 22:19, Alan Somers wrote:
> > We usually try to maintain backwards compatibility forever. But is that
> > necessary for the ses(4) ioctls? There are several problems with them as
> > currently defined.
On Thu, Sep 16, 2021 at 2:04 PM Mark Millard via freebsd-current <
freebsd-current@freebsd.org> wrote:
> What do I go about:
>
> QUOTE
> # zpool import
>pool: zopt0
> id: 18166787938870325966
> state: FAULTED
> status: One or more devices contains corrupted data.
> action: The pool can
On Thu, Sep 16, 2021 at 4:02 PM Mark Millard wrote:
>
>
> On 2021-Sep-16, at 13:39, Alan Somers wrote:
>
> > On Thu, Sep 16, 2021 at 2:04 PM Mark Millard via freebsd-current <
> freebsd-current@freebsd.org> wrote:
> > What do I go about:
> >
> >
tldr; should the Rust ecosystem ditch FreeBSD 10 compat for new code?
Rust uses FFI to talk to the OS's C library. That makes cross-compiling a
breeze. Unfortunately, it also fossilizes the ABI. FreeBSD's libc makes
careful use of ELF symbol versioning. That's how we were able to change
ino_t
On Mon, Sep 27, 2021 at 1:54 PM Mark Johnston wrote:
>
> On Thu, Aug 05, 2021 at 10:54:19AM -0500, Alan Somers wrote:
> > There's this:
> > https://openzfs.github.io/openzfs-docs/man/8/zpool-reguid.8.html . I
> > haven't used it myself.
>
> Would it be us
On Tue, Sep 28, 2021 at 9:48 AM Rodney W. Grimes
wrote:
>
> > On Mon, Sep 27, 2021 at 1:54 PM Mark Johnston wrote:
> > >
> > > On Thu, Aug 05, 2021 at 10:54:19AM -0500, Alan Somers wrote:
> > > > There's this:
> > > > https://openz
On Tue, Sep 28, 2021 at 10:15 AM Rodney W. Grimes
wrote:
>
> > On Tue, Sep 28, 2021 at 9:48 AM Rodney W. Grimes
> > wrote:
> > >
> > > > On Mon, Sep 27, 2021 at 1:54 PM Mark Johnston wrote:
> > > > >
> > > > > On Thu, Aug 05, 202
On Mon, Jan 8, 2018 at 5:31 PM Mateusz Guzik wrote:
>
> On Tue, Jan 9, 2018 at 12:41 AM, Michael Jung wrote:
>
> > On 2018-01-08 13:39, John Baldwin wrote:
> >
> >> On Tuesday, November 28, 2017 02:46:03 PM Michael Jung wrote:
> >>
> >>> Hi!
> >>>
> >>> I've recently up'd my processor count on ou
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
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.
> &
Google Compute Engine has images for 11.4-RELEASE, 12.2-RELEASE, and
13.0-RELEASE. Are there any images for current snapshots, and if so
what are their names?
-Alan
Thanks! That's just what I was looking for.
On Tue, Nov 16, 2021 at 9:20 PM Li-Wen Hsu wrote:
>
> On Wed, Nov 17, 2021 at 11:56 AM Alan Somers wrote:
> >
> > Google Compute Engine has images for 11.4-RELEASE, 12.2-RELEASE, and
> > 13.0-RELEASE. Are there any imag
On Sun, Dec 12, 2021 at 2:22 AM FreeBSD User wrote:
>
> Running CURRENT (FreeBSD 14.0-CURRENT #52 main-n251260-156fbc64857: Thu
> Dec 2 14:45:55 CET 2021 amd64), out of the sudden the ZFS RAIDZ pool
> suffered from an error:
>
> Solaris: WARNING: Pool 'POOL00' has encountered an uncorrectable I/O
On Sun, Dec 12, 2021 at 7:33 PM Frank Hwa wrote:
>
> Can you help me with the case I lost my root password for the dedicated
> server which has freebsd installed?
>
> Thanks in advance.
Easy, you just need console access. First reboot it. At the loader
prompt, select "Boot single user". Then a
tldr; this change allows the NFS server to export file systems that
use 64-bit directory cookies
https://reviews.freebsd.org/D33404
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260375
Long story:
NFSv2 included a 32-bit directory cookie with each readdir entry.
NFSv3 widened it to 64-bits, an
fspacectl(2) does for regular files the same thing that DIOCGDELETE
does for GEOM devices. The only differences are that DIOCGDELETE
requires the operation to be block-aligned, and if interrupted
DIOCGDELETE doesn't give feedback about partial progress. Can we
connect the two? That would allow a
On Thu, Apr 28, 2022 at 1:29 PM Marek Zarychta
wrote:
>
> W dniu 28.04.2022 o 21:21, FreeBSD User pisze:
> > Running XigmaNAS 12.3.0.4.9009 on amd64 hardware, we try to mount HDD to
> > rescue them and
> > store the data on ZFS volumes. Mounting of the HDD doesn't work, FreeBSD
> > 12.3 obviousl
On Tue, May 10, 2022 at 9:08 AM Cristian Cardoso
wrote:
>
> Hi
>
> I have some FreeBSD servers in my machine park and I would like to perform
> the version upgrade in an automated way with ansible.
>
> In my example, I want to perform the upgrade from version 12.3 to 13, it is
> possible to run
On Sat, Jun 4, 2022 at 1:04 PM Warner Losh wrote:
>
>
>
> On Sat, Jun 4, 2022, 11:13 AM Yuri wrote:
>>
>> Getting the following panic on HPE system with HPE enclosure:
>>
>> panic: make_dev_alias_v: bad si_name (error=22,
>> si_name=enc@n../type@0/slot@1/elmdesc@{"Name":"DriveBay1"}/pass4)
>>
Our /usr/include headers define a lot of symbols that are used by
critical utilities in the base system like ps and ifconfig, but aren't
stable across major releases. Since they aren't stable, utilities
built for older releases won't run correctly on newer ones. Would it
make sense to guard these
On Sat, Sep 3, 2022 at 11:10 PM Konstantin Belousov wrote:
>
> On Sat, Sep 03, 2022 at 10:19:12AM -0600, Alan Somers wrote:
> > Our /usr/include headers define a lot of symbols that are used by
> > critical utilities in the base system like ps and ifconfig, but aren't
On Mon, Sep 5, 2022 at 8:53 AM Mark Johnston wrote:
>
> On Mon, Sep 05, 2022 at 08:41:58AM -0600, Alan Somers wrote:
> > On Sat, Sep 3, 2022 at 11:10 PM Konstantin Belousov
> > wrote:
> > >
> > > On Sat, Sep 03, 2022 at 10:19:12AM -0600, Alan Somers wro
On Tue, Sep 6, 2022 at 9:07 AM Warner Losh wrote:
>
>
>
> On Tue, Sep 6, 2022 at 7:34 AM Konstantin Belousov
> wrote:
>>
>> On Mon, Sep 05, 2022 at 08:41:58AM -0600, Alan Somers wrote:
>> > On Sat, Sep 3, 2022 at 11:10 PM Konstantin Belousov
>> >
On Wed, Sep 7, 2022 at 8:55 AM Cy Schubert wrote:
>
> In message om>
> , Alan Somers writes:
> > On Sat, Sep 3, 2022 at 11:10 PM Konstantin Belousov
> > wro
> > te:
> > >
> > > On Sat, Sep 03, 2022 at 10:19:12AM -0600, Alan Somers wrote:
> >
On Tue, Sep 20, 2022 at 4:14 PM Nuno Teixeira wrote:
>
> Hello to all,
>
> I will use becl for the first time for current upgrades.
> Just to check that I'm thinking correctly:
>
> Create a test environment for upgrade:
> > bectl create -r test (should I use '-r'?)
> Activate test:
> > bectl activ
On Fri, Nov 25, 2022, 4:24 PM Rick Macklem wrote:
> Hi,
>
> bz@ has encouraged me to fiddle with the nfsd
> so that it works in a vnet jail.
> I have now basically done so, specifically for
> NFSv4, since NFSv3 presents various issues.
>
> What I have not yet done is put global variables
> in the
On Tue, Nov 29, 2022 at 5:21 PM Rick Macklem wrote:
>
>
>
> On Sun, Nov 27, 2022 at 10:04 AM Peter Eriksson wrote:
>>
>> Keep the global variables as defaults that apply to all nfsds and allow (at
>> least some subset) to be overridden inside the net jails if some things need
>> to be changed f
> I don't care for any of it. It looks like additional overhead with the
> addition of potential security risks. All for a very limited (and as yet
> unknown) use case.
Here's an example of a real-world use case. I'm responsible for
supporting multiple products involving NFS, iSCSI, and other
pro
If you're 100.0% percent sure that it will never be run, you can
delete it. But if you're only 99.9%, then I suggest converting it
into a KASSERT.
On Tue, Dec 13, 2022 at 3:20 PM Rick Macklem wrote:
>
> Hi,
>
> While working on getting mountd/nfsd to run in a vnet
> prison, I came across the fol
Unfortunately libzfs doesn't have a stable API, so this kind of
breakage is to be expected. libzfs_core does, but libzfs_core is
incomplete. You should report this problem upstream at
https://github.com/truenas/py-libzfs .
On Thu, Feb 2, 2023 at 2:37 AM Alexander Leidinger
wrote:
>
> Hi,
>
> th
Thanks! But for the record, what was the actual required change?
Could you like to the PR?
On Thu, Feb 2, 2023 at 8:44 AM Ryan Moeller wrote:
>
> I've updated the py-libzfs port to fix the build.
>
> --
> Ryan Moeller
> iXsystems, Inc.
> OS Developer
> Email: r...@ixsystems.com
On Mon, Feb 6, 2023 at 6:23 PM Rick Macklem wrote:
>
> PR#269328 reports an issue related to fspacectl() being
> mixed with mmap'd I/O.
>
> When working on a fix for this for the NFS client, I realized that
> "man fspacectl" does not clarify if the deallocation should commit
> changes to stable st
I'm planning to commit a change to the format of disk physical paths,
as reported by DIOCGPHYSPATH, and viewable by "diskinfo -v". This
will only affect disks in a SES enclosure (which are most SAS
enclosures with more than about 8 slots).
Technically, this is a backwards-incompatible change. Bu
I have servers with lots of RAM yet slow swap disks. So full crash
dumps are too slow. Instead, I use textdumps, which are theoretically
much faster. However, these servers also have about 10,000 threads
apiece, so textdumps are also slow. They take tens of minutes. I
have dual console setup:
On Thu, Apr 6, 2023 at 9:08 AM Alan Somers wrote:
>
> I have servers with lots of RAM yet slow swap disks. So full crash
> dumps are too slow. Instead, I use textdumps, which are theoretically
> much faster. However, these servers also have about 10,000 threads
> apiece, so tex
On Fri, Apr 7, 2023 at 2:22 AM Poul-Henning Kamp wrote:
>
> ----
> Alan Somers writes:
>
> > However, these servers also have about 10,000 threads
> > apiece, so textdumps are also slow. They take tens of minutes.
> > I have dual console setup: both serial a
On Fri, Apr 7, 2023 at 12:08 PM Warner Losh wrote:
>
>
>
> On Fri, Apr 7, 2023 at 6:20 AM Poul-Henning Kamp wrote:
>>
>>
>> Alan Somers writes:
>> > On Fri, Apr 7, 2023 at 2:22=E2=80=AFAM Poul-Henning Kamp
>> > wrote:
>>
>>
On Fri, Apr 7, 2023, 4:07 PM Rodney W. Grimes
wrote:
> > On Fri, Apr 7, 2023 at 12:08?PM Warner Losh wrote:
> > >
> > >
> > >
> > > On Fri, Apr 7, 2023 at 6:20?AM Poul-Henning Kamp
> wrote:
> > >>
> > >>
> >
Thanks for the head's up. Hopefully I'll be able to look at it later this week.
On Mon, Apr 10, 2023 at 4:40 PM Jamie Landeg-Jones wrote:
>
> There is a replicable problem with file closing on fusefs, since
> 0bade34633f997c22f5e4e0931df0d534f560a38, Alan Somers
> 202
On Wed, May 17, 2023 at 9:44 AM Rick Macklem wrote:
>
> So, the subject line basically says it.
> I do a git cherry-pick to MFC. It works, but the resultant file(s) are not
> correct. What do I do to fix this?
> (If the merge fails, then it's easy, but there doesn't seem to be an option
> on cher
New builds of stable/13, stable/12, and current used to appear in
Google Cloud about once per week. But the latest builds all date from
13-April-2023. Does some script need to be kicked? To see the
currently available images, do:
pkg install google-cloud-sdk
gcloud compute images list --project
On Mon, Jun 19, 2023 at 12:11 PM Alan Somers wrote:
>
> New builds of stable/13, stable/12, and current used to appear in
> Google Cloud about once per week. But the latest builds all date from
> 13-April-2023. Does some script need to be kicked? To see the
> currently avail
On Tue, Aug 8, 2023 at 10:08 AM Dag-Erling Smørgrav wrote:
>
> At some point between 42d088299c (4 May) and f0c9703301 (26 June), a
> deadlock was introduced in ZFS. It is still present as of 9c2823bae9 (4
> August) and is 100% reproducable just by starting poudriere bulk in a
> 16-core VM and wa
With ZFS, you might be using transparent compression. "du -sh" will
show you a file's compressed size. But "ls -lh" will show you the
logical size. That's probably why the tarball looked so much bigger
than the ports tree on the first system. If you do "du -sh" on the
tarball, I bet you'll see
On Wed, Dec 5, 2018 at 10:18 PM Jia-Shiun Li wrote:
>
> amd64 and RPi3 do not have this issue.
>
> jsli@rpi2:/home/jsli 13:04 # uname -a
> FreeBSD rpi2 13.0-CURRENT FreeBSD 13.0-CURRENT r341419 GENERIC-NODEBUG arm
> jsli@rpi2:/home/jsli 13:05 # mount -t tmpfs tmpfs /mnt
> jsli@rpi2:/home/jsli 13:
On Sun, Feb 10, 2019 at 2:27 PM David Boyd wrote:
>
> In 13.0-CURRENT, dialog(1) fills lines shorter than the box width with
> something other than the background color. In an xterm session, the
> fill is white. In a console session, the fill is black.
>
> This appears to be a regression in the d
On Sun, Feb 10, 2019 at 5:51 PM Rick Macklem wrote:
>
> I am finally back to looking at an old PR#205193.
>
> The problem is that the nfsuserd daemon expects upcalls from the kernel
> that are from localhost (127.0.0.1) and when jails are running on the system,
> 127.0.0.1 is mapped to some other
Is he trying to send the kqueue file descriptor itself using sendmsg
with SCM_RIGHTS? It sounds like kqueues cannot be sent over unix
sockets; not every file type necessarily can. But if you want to know
the nitty-gritty details, just run this:
dtrace -i 'fbt:::return /arg1 == 45/ {stack();}' -c
On Mon, Mar 18, 2019 at 9:38 AM Andriy Gapon wrote:
>
> On 18/03/2019 17:32, Konstantin Belousov wrote:
> > On Mon, Mar 18, 2019 at 05:20:35PM +0200, Andriy Gapon wrote:
> >>
> >> First, a note that this was observed on a system that runs a fairly old
> >> current
> >> (~ 1 year old) with a fairl
fusefs has several sysctl knobs that seem to be workarounds for bugs
in particular fuse daemons. However, there is no indication as to
which those daemons are, neither in the code nor in SVN. All of the
workarounds are at least 6.5 years old, so the original bugs may have
been fixed already. Sin
On Thu, Mar 21, 2019 at 9:49 AM Shawn Webb wrote:
>
> Hey Alan,
>
> Thank you very much for your work in maintaining fusefs. I only use
> fusefs in very limited circumstances, so take what I'm about to say
> with a grain of salt.
>
> On Thu, Mar 21, 2019 at 09:43:
On Thu, Mar 21, 2019 at 10:00 AM Shawn Webb wrote:
>
> On Thu, Mar 21, 2019 at 09:55:15AM -0600, Alan Somers wrote:
> > On Thu, Mar 21, 2019 at 9:49 AM Shawn Webb
> > wrote:
> > >
> > > Hey Alan,
> > >
> > > Thank you very much for your
On Fri, Apr 5, 2019 at 11:48 PM Marek Zarychta <
zarych...@plan-b.pwste.edu.pl> wrote:
>
> W dniu 21.03.2019 o 17:03, Alan Somers pisze:
> > On Thu, Mar 21, 2019 at 10:00 AM Shawn Webb
> wrote:
> >> On Thu, Mar 21, 2019 at 09:55:15AM -0600, Alan Somers wrote:
>
On Sat, Apr 6, 2019 at 8:52 AM Marek Zarychta
wrote:
>
> W dniu 06.04.2019 o 15:39, Alan Somers pisze:
> > On Fri, Apr 5, 2019 at 11:48 PM Marek Zarychta <
> > zarych...@plan-b.pwste.edu.pl> wrote:
> >
> >> W dniu 21.03.2019 o 17:03, Alan Somers pisze:
On Wed, May 1, 2019 at 5:18 AM Michelle Sullivan wrote:
>
> FYI - newly installed:
>
> lock order reversal:
> 1st 0xf80004f77608 ufs (ufs) @ /usr/src/sys/kern/vfs_lookup.c:713
> 2nd 0xfe80edc0 bufwait (bufwait) @
> /usr/src/sys/ufs/ffs/ffs_vnops.c:283
> 3rd 0xf80006aff248 ufs
See r346959. Before first boot, you should expand the image up to
whatever size you want. growfs(8) will automatically expand the file
system.
-Alan
On Fri, May 3, 2019 at 10:32 AM David Boyd wrote:
>
> The vm-image for 13.0-CURRENT
>
> FreeBSD-13.0-CURRENT-amd64-20190503-r347033.vmdk
On Fri, May 3, 2019 at 7:40 PM bob prohaska wrote:
>
> On Fri, May 03, 2019 at 11:06:15AM -0700, Rodney W. Grimes wrote:
> > -- Start of PGP signed section.
> > > On Fri, May 03, 2019 at 10:12:58AM -0700, Enji Cooper wrote:
> > > >
> > > > >
On Sat, May 18, 2019 at 7:59 PM Rick Macklem wrote:
>
> Hi,
>
> I've been working with Peter Errikson on a patch for mountd that adds a new
> option
> for incremental updating of exports. This seems to be helping a lot w.r.t.
> performance
> on an NFS server with lots (1+) of exported file s
On Wed, May 22, 2019 at 11:59 AM Johannes Lundberg wrote:
>
>
> On 5/22/19 10:51 AM, Konstantin Belousov wrote:
> > On Wed, May 22, 2019 at 10:36:34AM -0700, Johannes Lundberg wrote:
> >> Hi
> >>
> >> I'm fiddling with lindebugfs, which is based on pseudofs. When writing
> >> to a file,
> >>
> >>
On Wed, May 22, 2019 at 5:18 PM Johannes Lundberg wrote:
>
>
> On 5/22/19 4:12 PM, Johannes Lundberg wrote:
> > On 5/22/19 3:02 PM, Conrad Meyer wrote:
> >> On Wed, May 22, 2019 at 1:58 PM Johannes Lundberg
> >> wrote:
> It seems, a single '>' will cause it to try to create the file (even
>
On Wed, May 22, 2019 at 5:33 PM Johannes Lundberg wrote:
>
>
> On 5/22/19 4:22 PM, Alan Somers wrote:
> > On Wed, May 22, 2019 at 5:18 PM Johannes Lundberg
> > wrote:
> >>
> >> On 5/22/19 4:12 PM, Johannes Lundberg wrote:
> >>> On 5/22/19 3:02
Does anybody know how to check out a local copy of the CSRG
repository? I can view it with ViewVC, but I would really like local
access. It doesn't seem to be available on the usual repo.FreeBSD.org
or svn.FreeBSD.org.
$ svn checkout https://svn.FreeBSD.org/csrg csrg
svn: E170013: Unable to conn
On Wed, Jun 19, 2019 at 5:38 PM Warner Losh wrote:
>
>
>
> On Wed, Jun 19, 2019 at 1:14 PM Alan Somers wrote:
>>
>> Does anybody know how to check out a local copy of the CSRG
>> repository? I can view it with ViewVC, but I would really like local
>> access.
On Wed, Jun 19, 2019 at 8:41 PM Warner Losh wrote:
>
>
>
> On Wed, Jun 19, 2019, 7:09 PM Alan Somers wrote:
>>
>> On Wed, Jun 19, 2019 at 5:38 PM Warner Losh wrote:
>> >
>> >
>> >
>> > On Wed, Jun 19, 2019 at 1:14 PM Alan Somers w
On Thu, Jun 20, 2019 at 7:40 AM Rodney W. Grimes
wrote:
>
> > On 19-06-20 05 h 59, Warner Losh wrote:
> > > On Wed, Jun 19, 2019 at 7:55 PM Alan Somers wrote:
> > >
> > >> On Wed, Jun 19, 2019 at 8:41 PM Warner Losh wrote:
> > >>>
>
I panic my development VM regularly. Each time, I need to fsck the
file system. Even if I had run sync(8) just before the panic, I
frequently find corruption. What should I change to make sync(8)
work, or at least to make corruption rare? It looks like my root file
system is using soft-updates+
On Fri, Jun 21, 2019 at 1:56 PM Scott Long wrote:
>
>
>
> > On Jun 21, 2019, at 1:49 PM, Alan Somers wrote:
> >
> > I panic my development VM regularly. Each time, I need to fsck the
> > file system. Even if I had run sync(8) just before the panic, I
>
On Fri, Jun 21, 2019 at 3:51 PM Scott Long wrote:
>
>
>
> > On Jun 21, 2019, at 3:49 PM, Don Lewis wrote:
> >
> > On 21 Jun, Scott Long wrote:
> >>
> >>> On Jun 21, 2019, at 2:09 PM, Alan Somers wrote:
> >>
On Fri, Jun 21, 2019 at 4:50 PM Warner Losh wrote:
>
>
>
> On Fri, Jun 21, 2019, 3:44 PM Scott Long wrote:
>>
>>
>>
>> > On Jun 21, 2019, at 4:37 PM, Warner Losh wrote:
>> >
>> > On Fri, Jun 21, 2019, 3:33 PM Conrad Meyer wrote:
>
On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote:
>
> I have a little program for testing the copy_file_range(2) syscall I've been
> working on. (The current version is attached, in case anyone is interested.)
>
> It take a few minutes to run on a slow system and uses about 6Gbytes of disk
> spac
On Thu, Jul 4, 2019 at 6:29 PM Rick Macklem wrote:
>
> Hi,
>
> I have been working on a Linux compatible copy_file_range(2) syscall
> (the current code can be found at https://reviews.freebsd.org/D20584).
>
> One outstanding issue is how it should deal with signals.
> Right now, I have vn_start_wr
On Fri, Jul 5, 2019 at 9:11 AM Rick Macklem wrote:
>
> Alan Somers wrote:
> >On Thu, Jul 4, 2019 at 6:38 PM Rick Macklem wrote:
> >>
> >> I have a little program for testing the copy_file_range(2) syscall I've
> >> been
> >> working on
On Fri, Jul 5, 2019 at 9:28 AM Rick Macklem wrote:
>
> jilles wrote in copy_file_range.2:99
> > The Linux man page (from
> > http://man7.org/linux/man->pages/man2/copy_file_range.2.html ) says that a
> > non-zero flags argument will cause >the call to return an [EINVAL] error. I
> > think that
On Thu, Jul 25, 2019 at 12:05 PM Larry Rosenman wrote:
>
> Um Who broke this?
>
> ===> Building for lsof-4.93.2_2,8
> (cd lib; /usr/bin/make DEBUG="-O2" CFGF="-pipe -fstack-protector-strong
> -fno-strict-aliasing -DNEEDS_BOOL_TYPEDEF -DHASTASKS -DHAS_PAUSE_SBT
> -DHAS_DUP2 -DHAS_CLOSEFROM -D
On Thu, Jul 25, 2019 at 12:13 PM Larry Rosenman wrote:
>
> On 07/25/2019 1:10 pm, Alan Somers wrote:
> > On Thu, Jul 25, 2019 at 12:05 PM Larry Rosenman
> > wrote:
> >>
> >> Um Who broke this?
> >>
> >> /usr/src/sys/sys/refcount.h:
On Thu, Aug 8, 2019 at 7:42 AM Michael Tuexen wrote:
>
>
>
> > On 8. Aug 2019, at 14:24, Slava Shwartsman wrote:
> >
> > Apparently, Bullseye are dropping support for FreeBSD.
> >
> > We are looking for an alternative for kernel module run time analysis.
> > Mostly interested in code coverage (fo
The new FUSE driver has just landed in current. It raises the protocol
level from 7.8 to 7.23, fixes many bugs, adds a test suite for the
driver, and adds many new features. New features include:
* Optional kernel-side permissions checks (-o default_permissions)
* Implement VOP_MKNOD, VOP_BMAP,
t sure where that comes from.
> -M
>
> On Thu, Aug 8, 2019 at 6:52 AM Alan Somers wrote:
> >
> > On Thu, Aug 8, 2019 at 7:42 AM Michael Tuexen wrote:
> > >
> > >
> > >
> > > > On 8. Aug 2019, at 14:24, Slava Shwartsman
d Forum, and
> try to learn all I can. So do you have any specific suggestions for programs
> to install and test FUSE? I kind of like the no-x console & the Xterminal
> window too, and dabble with clang cc (strictly C, no C++) and Python too. Let
> me know.
>
> Clay Daniels
>
&g
On Fri, Aug 9, 2019 at 3:02 AM Gary Jennejohn wrote:
>
> On Thu, 8 Aug 2019 12:34:52 -0600
> Alan Somers wrote:
>
> [snip]
>
> > VM images:
> > http://ftp0.nyi.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/13.0-CURRENT/amd64/20190808/
> > ISOs: http://ftp0.n
On Fri, Aug 9, 2019 at 7:38 AM Gary Jennejohn wrote:
>
> On Fri, 9 Aug 2019 06:49:36 -0600
> Alan Somers wrote:
>
> [snip test results]
>
> > Thanks for the report, Gary. BTW, fusefs mounts are only
> > interruptible when mounted with "-o intr". If
On Sat, Aug 10, 2019 at 8:03 PM Rick Macklem wrote:
>
> Hi,
>
> I've noticed that, if you do a lseek(SEEK_DATA/SEEK_HOLE) on a file that
> resides in a file system that does not support holes, ENOTTY is returned.
>
> This error isn't listed for lseek() and seems a liitle weird.
>
> I can see a cou
On Sun, Aug 11, 2019 at 8:57 AM Ian Lepore wrote:
>
> On Sun, 2019-08-11 at 09:04 +0200, Gary Jennejohn wrote:
> > On Sun, 11 Aug 2019 02:03:10 +
> > Rick Macklem wrote:
> >
> > > Hi,
> > >
> > > I've noticed that, if you do a lseek(SEEK_DATA/SEEK_HOLE) on a file
> > > that
> > > resides in a
On Mon, Aug 19, 2019 at 5:39 AM David Wolfskill wrote:
>
> "df" (without the mountpoint specification) is normal, but specifying
> the mountpoint appears to cause a large number of "space" characters
> to be emitted after "Filesystem" in the heading, and the actual
> "filesystem" data to be elided
In freebsd head, the driver is now called fusefs.ko. Does that help?
On Fri, Aug 30, 2019, 12:45 PM Clay Daniels Jr.
wrote:
> I finally have a little time to play with the FUSE, and installed some
> fusefs utilities I might like to try, for ntfs & ext. This is what I have:
> ---
> clay@bsd13:~
101 - 200 of 292 matches
Mail list logo
