On 21 Jun, 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 Fri, Jun 21, 2019 at 2:55 PM Alan Somers wrote:
I would've thought that immediately following a sync(8), the
filesystem would be con
Thank you for all your work on FreeBSD. Wish you luck in your new job.
Kind regards
Miroslav Lachman
Glen Barber wrote on 2019/06/20 18:22:
Dear FreeBSD community:
As I have a highly-visible role within the community, I want to share
some news. I have decided the time has come to move on fro
On Fri, 21 Jun 2019 13:49:30 -0600
Alan Somers wrote:
> I panic my development VM regularly. Each time, I need to fsck the
> file system.
I've found UFS on gjournal to be reliable.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.or
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 Fri, Jun 21, 2019 at 2:55 PM Alan Somers 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 Fri, Jun 21, 2019 at 2:55 PM Alan Somers
> wrote:
> >>> I would've thought that immediately following a sync(8), the
> >
(Please send the followup discussions to freebsd-testing@ list.)
FreeBSD CI Weekly Report 2019-06-16
===
Here is a summary of the FreeBSD Continuous Integration results for
the period from 2019-06-10 to 2019-06-16.
During this period, we have:
* 1927 builds (98.1
> On Jun 21, 2019, at 4:37 PM, Warner Losh wrote:
>
> On Fri, Jun 21, 2019, 3:33 PM Conrad Meyer wrote:
>
>> On Fri, Jun 21, 2019 at 2:55 PM Alan Somers wrote:
>>> I would've thought that immediately following a sync(8), the
>>> filesystem would be consistent. Why do I still see errors afte
On Fri, Jun 21, 2019, 3:33 PM Conrad Meyer wrote:
> On Fri, Jun 21, 2019 at 2:55 PM Alan Somers wrote:
> > I would've thought that immediately following a sync(8), the
> > filesystem would be consistent. Why do I still see errors after a
> > panic in files that were written before I sync()ed?
>
Alan Somers wrote:
> I would've thought that immediately following a sync(8), the
> filesystem would be consistent. Why do I still see errors after a
sync(8) does little more than tell the kernel to start flushing some
pages - which the kernel would do anyway in about 30s
So, it does not really
On Fri, Jun 21, 2019 at 2:55 PM Alan Somers wrote:
> I would've thought that immediately following a sync(8), the
> filesystem would be consistent. Why do I still see errors after a
> panic in files that were written before I sync()ed?
> -Alan
Hi Alan,
Contra the name, sync(2) (sync(8)) isn't s
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 1:56 PM Scott Long wrote:
>
>
>
> > On
> 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 1:56 PM Scott Long wrote:
> On Jun 21, 2019, at 1:49 PM, Alan Somers wrote:
>
> I panic my
On 21 Jun, Scott Long wrote:
>
>> On Jun 21, 2019, at 2:09 PM, Alan Somers wrote:
>>
>> 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
> On Jun 21, 2019, at 2:09 PM, Alan Somers wrote:
>
> 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
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
> > frequently find corruption. What should
> 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
> frequently find corruption. What should I change to make sync(8)
> work, or at least to make corruptio
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, 7:44 AM Scott Long wrote:
>
>
> > On Jun 17, 2019, at 7:46 PM, Julian H. Stacey wrote:
> >
> >>>
> >>> Stop.
> >>> make[3]: stopped in /usr/src/usr.bin/mkesdb_static
> >>>
> >>> A double waste of CPU & human time & power in a hot office.
> >>> Commit bits used to be suspend
> On Jun 17, 2019, at 7:46 PM, Julian H. Stacey wrote:
>
>>>
>>> Stop.
>>> make[3]: stopped in /usr/src/usr.bin/mkesdb_static
>>>
>>> A double waste of CPU & human time & power in a hot office.
>>> Commit bits used to be suspended for un-buildable code. I'll boot
>>> stable.
>>
>> Since you
Since r349169, my Rock64 has consistently panic'd whilst attaching
rockchip_dwmmc1. A kernel built at r349135 works OK. The relevant
output looks like:
rockchip_dwmmc0: mem 0xff50-0xff503fff irq 40 on ofwbus0
rockchip_dwmmc0: Hardware version ID is 270a
mmc0: on rockchip_dwmmc0
rockchip_dwm
Thank you Glen for all your hard work and time and good luck with the
new job.
regards
Johan
Op 20-06-19 om 18:22 schreef Glen Barber:
> Dear FreeBSD community:
>
> As I have a highly-visible role within the community, I want to share
> some news. I have decided the time has come to move on from
21 matches
Mail list logo
