I have extracted material from the list-exchanges
related to this and submitted:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220693
against the kernel for the issue.
I placed emphasis on the SSD-trim related "freeing
free block" panics that "fsck -B" can lead to
after it gets the g_vfs_don
> 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
[This note has more information than one sent with extra text
in the subject but with a partially different "to" list.]
Peter Jeremy peter at rulingia.com wrote on
Sat Jul 8 02:00:47 UTC 2017 :
> When did you first notice this (what SVN revision)?
> Do you know what the last good SVN revision was
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 (what SVN revision)?
I wa
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 (what SVN revision)?
Do you know what the last good SVN revision was?
On 2017-Jul-7, at 4:49 PM, Michael Butler wrote:
> On 07/07/17 19:02, Mark Millard wrote:
>> Michael Butler imb at protected-networks.net wrote on
>> Fri Jul 7 14:45:12 UTC 2017 :
>>> Recent builds doing a backup (dump) cause nonsensical errors in syslog:
>>>
>>> Jul 7 00:10:24 toshi kernel:
On 07/07/17 19:02, Mark Millard wrote:
Michael Butler imb at protected-networks.net wrote on
Fri Jul 7 14:45:12 UTC 2017 :
Recent builds doing a backup (dump) cause nonsensical errors in syslog:
Jul 7 00:10:24 toshi kernel:
g_vfs_done():ada0s3a[READ(offset=6050375794688, length=32768)]error
Michael Butler imb at protected-networks.net wrote on
Fri Jul 7 14:45:12 UTC 2017 :
> Recent builds doing a backup (dump) cause nonsensical errors in syslog:
>
> Jul 7 00:10:24 toshi kernel:
> g_vfs_done():ada0s3a[READ(offset=6050375794688, length=32768)]error = 5
> Jul 7 00:10:24 toshi kern
Recent builds doing a backup (dump) cause nonsensical errors in syslog:
Jul 7 00:10:24 toshi kernel:
g_vfs_done():ada0s3a[READ(offset=6050375794688, length=32768)]error = 5
Jul 7 00:10:24 toshi kernel:
g_vfs_done():ada0s3a[READ(offset=546222112768, length=32768)]error = 5
Jul 7 00:10:24 tosh
13 matches
Mail list logo
