(Please send the followup discussions to freebsd-testing@ list.)
FreeBSD CI Weekly Report 2019-06-02
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-05-27 to 2019-06-02.
During this period, we have:
* 1752 builds (97.8
On Wed, Jun 5, 2019 at 2:42 PM Mark Saad wrote:
>
> On Wed, Jun 5, 2019 at 12:29 PM Mark Saad wrote:
> >
> > All
> > I was wondering if anyone could shed some light on this boot panic I
> > saw yesterday. This is on a Dell R630 with Bios 2.9.1 booting
> > 12.0-STABLE-r348203 amd64.
> > I revert
On Wed, Jun 5, 2019 at 12:29 PM Mark Saad wrote:
>
> All
> I was wondering if anyone could shed some light on this boot panic I
> saw yesterday. This is on a Dell R630 with Bios 2.9.1 booting
> 12.0-STABLE-r348203 amd64.
> I reverted this back to 12.0-RELEASE-p4 and its fine .
>
> The only custo
All
I was wondering if anyone could shed some light on this boot panic I
saw yesterday. This is on a Dell R630 with Bios 2.9.1 booting
12.0-STABLE-r348203 amd64.
I reverted this back to 12.0-RELEASE-p4 and its fine .
The only custom options I had were in loader.conf
kern.geom.label.gptid.enable
Hello,
In the logs I don't have any output about problems with the filesystem.
Indeed I had a corrupted file after learning about the zpool status -v, but
the ones that I can't delete didn't show up.
Searching on the web I found that running the command #echo >
/path/to/undetelable/file seems to f
On 2019-06-05 8:14 am, Mario Olofo wrote:
Hello guys,
I'm configuring a new installation of FreeBSD-12.0-RELEASE and
installed
with ZFS for the root file system.
I run the command zfs set compression=lz4 root, and after this, the
system
become a little weird.
I tried to test some npm install
Hello guys,
I'm configuring a new installation of FreeBSD-12.0-RELEASE and installed
with ZFS for the root file system.
I run the command zfs set compression=lz4 root, and after this, the system
become a little weird.
I tried to test some npm install to see if the compression was working and
it is
