> On 07/08/17 12:28, Rodney W. Grimes wrote:
>
> > Since it has been speculated that this is occuring during the
> > creation of the snapshot, could you try just creating a snapshot
> > using mksnap_ffs and see if any errors occur?
>
> After a short pause with disk activity, the same sorts of err
[A normal multi-user boot's fsck activity can do
fsck -B activity that gets the problem.]
On 2017-Jul-8, at 9:45 AM, Mark Millard wrote:
> [I add notes about a problem that happens after the
> "fsck -B". Also forgot to mention: production style
> kernel world builds were in use. And a tried a
[I add notes about a problem that happens after the
"fsck -B". Also forgot to mention: production style
kernel world builds were in use. And a tried a
powerpc64 build and it works the same.]
On 2017-Jul-7, at 11:09 PM, Mark Millard wrote:
> [This note has more information than one sent with ext
> On 07/07/17 21:53, Peter Jeremy wrote:
> > On 2017-Jul-07 10:44:36 -0400, Michael Butler
> > wrote:
> >> Recent builds doing a backup (dump) cause nonsensical errors in syslog:
> >
> > I can't directly offer any ideas but some more background might help:
> > When did you first notice this (wha
On 07/08/17 12:28, Rodney W. Grimes wrote:
Since it has been speculated that this is occuring during the
creation of the snapshot, could you try just creating a snapshot
using mksnap_ffs and see if any errors occur?
After a short pause with disk activity, the same sorts of errors are
logged w
Hi All,
I use own pkg base repository. Today I tried to install packages
on a new system. However, pkg refused to use my repo, since it's
certificate is expired (several days). That's good.
However, pkg happily update packages at other systems. So, seems
that pkg does not perform checks / validat
Hi All,
I tied to install a new FreeBSD-amd-12 system from official USB
installation memstick.img. Auto-UFS (GPT) installs fine and the system
boots fine. However, ZFS-Auto install succeeds, but is not loaded.
At the very beginning it gives something like "gpt sector error,
gpt sector 1 error