search for: pseudofiles

...BTW, I'm not sure it's necessary to escape the #. I never tried it without. Also note that it flattens the remote host's mount tree into a single filesystem - so things like /proc look like they are in the same filesystem as /. This can lead to backing up /proc's contents (many pseudofiles), if you don't exclude it, even if you use rsync's -x option. On Sun, Mar 25, 2018 at 6:43 AM, Marc Roos via rsync <rsync at lists.samba.org> wrote: > > I still stuck with these errors > > packet_write_wait: Connection to 192.168.10.43 port 22: Broken pipe > rsync: con...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

...t's necessary to escape the #. I never tried it without. > > Also note that it flattens the remote host's mount tree into a single > filesystem - so things like /proc look like they are in the same > filesystem as /. This can lead to backing up /proc's contents (many > pseudofiles), if you don't exclude it, even if you use rsync's -x > option. > > On Sun, Mar 25, 2018 at 6:43 AM, Marc Roos via rsync > <rsync at lists.samba.org> wrote: >> >> I still stuck with these errors >> >> packet_write_wait: Connection to 192.168.10.43...

Does ZFS currently attempt to group metadata in large sector-ranges on the disk? Can this be expected to happen "automagically" - i.e. during each TXG close we have to COW-update whole branches of the blockpointer tree, so these new blocks might "just happen" to always coalesce into larger sector groups? Rationale: larger regions dedicated to smallish block pointers might be

...ape the #. I never tried it > without. >> >> Also note that it flattens the remote host's mount tree into a single >> filesystem - so things like /proc look like they are in the same >> filesystem as /. This can lead to backing up /proc's contents (many >> pseudofiles), if you don't exclude it, even if you use rsync's -x >> option. >> >> On Sun, Mar 25, 2018 at 6:43 AM, Marc Roos via rsync >> <rsync at lists.samba.org> wrote: >>> >>> I still stuck with these errors >>> >>> packet_write_wai...

...the #. I never tried it > without. >> >> Also note that it flattens the remote host's mount tree into a single >> filesystem - so things like /proc look like they are in the same >> filesystem as /. This can lead to backing up /proc's contents (many >> pseudofiles), if you don't exclude it, even if you use rsync's -x >> option. >> >> On Sun, Mar 25, 2018 at 6:43 AM, Marc Roos via rsync >> <rsync at lists.samba.org> wrote: >>> >>> I still stuck with these errors >>> >>> packet_write_w...