Re: Updating to FreeBSD-current, can't mount -uw /

[Warner Losh]

On Sun, Jun 6, 2021 at 5:24 AM Thomas Mueller  wrote:

> I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld
> took 11:15 (hours:minutes), buildkernel was also successful, I even
> appeared to be successful with "dhclient re0".
>
> UPDATING file says to boot single-user after buildkernel and
> installkernel, but then mount -u / or mount -uw / does not work as it did
> in previous times.
>
> Results were
>
> mount -uw / or mount -u / produces
> fstab: /etc/fstab:2: Inappropriate file type or format
> fstab: /etc/fstab:2: Inappropriate file type or format
>
> /etc/fstab
> # DeviceMountpoint  FStype  Options DumpPass#
> /dev/gpt/Sea1-08  none swap 0   0
> /dev/gpt/Sea1-18  / ufs rw  1   1
> #/dev/gpt/Sea1-06 /home   ufs  rw 1  1
>
> fsck -p produces
>
> fstab: /etc/fstab:2: Inappropriate file type or format
> /dev/gpt/Sea1-18: NO WRITE ACCESS
> /dev/gpt/Sea1-18: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
>
> I tried fsck /dev/gpt/Sea1-18 and fsck / but did no better.
>
> Now what do I do?  I also ran fsck_ffs instead of just fsck.
>
> Do I need to boot NetBSD and run fsck_ffs or fsck_ffs -f from there?
>

fsck /dev/gpt/Seae1-18

doesn't work? You can also fsck on the underlying disk, but since there's
many choices
that are hard to know w/o a dmesg.

Warner

Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

[Thomas Mueller]

I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took 
11:15 (hours:minutes), buildkernel was also successful, I even appeared to be 
successful with "dhclient re0".

UPDATING file says to boot single-user after buildkernel and installkernel, but 
then mount -u / or mount -uw / does not work as it did in previous times.

Results were

mount -uw / or mount -u / produces 
fstab: /etc/fstab:2: Inappropriate file type or format
fstab: /etc/fstab:2: Inappropriate file type or format

/etc/fstab
# DeviceMountpoint  FStype  Options DumpPass#
/dev/gpt/Sea1-08  none swap 0   0
/dev/gpt/Sea1-18  / ufs rw  1   1
#/dev/gpt/Sea1-06 /home   ufs  rw 1  1

fsck -p produces

fstab: /etc/fstab:2: Inappropriate file type or format
/dev/gpt/Sea1-18: NO WRITE ACCESS
/dev/gpt/Sea1-18: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

I tried fsck /dev/gpt/Sea1-18 and fsck / but did no better.

Now what do I do?  I also ran fsck_ffs instead of just fsck.

Do I need to boot NetBSD and run fsck_ffs or fsck_ffs -f from there?

Now I seem to have solved the problem.  Either rebooting or fixing /etc/fstab 
did it.

I may have had one too few fields on the /dev/gpt/Sea1-08 line, maybe that 
caused the system to misinterpret the next line.

I added sw between swap and 0, thus the corrected fstab is

# DeviceMountpoint  FStype  Options DumpPass#
/dev/gpt/Sea1-08  none swap sw  0   0
/dev/gpt/Sea1-18  / ufs rw  1   1
#/dev/gpt/Sea1-06 /home   ufs  rw 1  1

Now I see from the emailing lists that etcupdate is replacing mergemaster, but 
UPDATING file still says to use mergemaster without mentioning etcupdate.

Developers, please update!

There are differences between NetBSD's etcupdate and FreeBSD's etcupdate.  I 
don't want to do the wrong thing in FreeBSD. 

Tom

Re: What happen to mailing list archives?

[Mark Millard via freebsd-current]

Baptiste Daroussin  wrote on
Date: Sun, 6 Jun 2021 10:53:49 +0200 :

> What has happended:
> plan A: we migrated everything off mailman/pipermail seamlessly with 
> redirection
> and so on. We patched the new archiver to produce the same file names has
> pipermail
> 
> Plan A worked fine up to a limit, there was plenty of hand edition in the 
> past,
> we we decided to move to plan B which is what is happening now.
> 
> Plan B: We keep a frozen version of the archives up to the migration date 
> under
> the pipermail directory and have the new archives created in the archives
> directory.
> 
> All the pipermail archives have been restored as they were. The new archives
> receives in their index a new link to point people to the pipermails archive 
> if
> looking for older archives.
> 
> this has been done a couple of hours ago (before Steve emails) during a 
> window,
> of ~ 10 hours, the mailing lists which slow traffic aka the one which didn't
> received any email since the migration ended up with an empty "archives"
> directory (aka a 404), a file with explanation and redirection to pipermail 
> has
> been installed there.
> 
> Some work is still needed for the mailing lists which has been transformed as
> readonly, this will be done in the next couple of days

It is too bad that a reference to a "no examples yet"
month, such as, (at the time I write this):

https://lists.freebsd.org/archives/freebsd-toolchain/2021-June/date.html

does not show at least (Date view specific example):

• Other periods:[ Previous, Date view ] [ List of Folders ]
• Other: [ Actives mailing lists ] [ Archives from mailman's time ]

when there are prior months available in
https://lists.freebsd.org/archives/ or show at least just:

• Other: [ Actives mailing lists ] [ Archives from mailman's time ]

when no prior months are available there.


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)

Re: What happen to mailing list archives?

[Rainer Hurling]

Hi Steve,

Am 06.06.21 um 01:13 schrieb Steve Kargl:
> On Sun, Jun 06, 2021 at 01:00:40AM +0200, Michael Gmelin wrote:
>>
>>
>>> On 6. Jun 2021, at 00:53, Steve Kargl  
>>> wrote:
>>>
>>> It seems someone has tried to migrate the mailing list archives
>>> from mailman to some new fangle code.  This has broken the archives
>>> for at least freebsd-numerics@, freebsd-office@, freebsd-net@
>>>
>>> As a comparison, simply go to
>>>
>>> https://lists.freebsd.org/mailman/listinfo
>>>
>>> and follow the links to freebsd-numerics and freebsd-toolchain.
>>>
>>> Can this be fixed?
>>>
>>
>> New archives are here:
>> https://lists.freebsd.org/archives/
>>
> 
> If I go to https://www.freebsd.org/community/mailinglists/
> 
> I see the lines
> 
>   Mailing list archives
> 
>   You can search or browse the mailing list archives at www.FreeBSD.org.
>   It is also possible to browse the mailing lists via the Mailman Web
>   interface.
> 
> Both instances of the word "browse" are hyperlinks.  If I click of the
> second "browse" link, then I end up at
> 
> https://lists.freebsd.org/mailman/listinfo
> 
> which presents a list of archives, you'll see freebsd-numerics
> is a hyperlink (as well as many others).  If I click on freebsd-numerics,
> this takes me to
> 
> https://lists.freebsd.org/subscription/freebsd-numerics
> 
> which displays
> 
>   Subscription for freebsd-numerics
> 
>  Browse the archives: here
>  (and 6 hyperlinks for subscribing and unsubscribing).
> 
> If I click on "here", I get

When I click on "here" I also get a "404 Not Found" at first, but only
for about 5 seconds. This is followed by a redirect to the archive list.
Maybe try it again?

If that doesn't work for you: I have saved some threads with Bruce Evans
locally. I could provide them, hoping that there is something useful?

Regards,
Rainer


> 
> 404 Not Found
> 
> Ergo, the freebsd-numerics archive is unreachable from the "here" link.
> Shouldn't this redirect to the new fangle way?
> 

Updating to FreeBSD-current, can't mount -uw /

[Thomas Mueller]

I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took 
11:15 (hours:minutes), buildkernel was also successful, I even appeared to be 
successful with "dhclient re0".

UPDATING file says to boot single-user after buildkernel and installkernel, but 
then mount -u / or mount -uw / does not work as it did in previous times.

Results were

mount -uw / or mount -u / produces 
fstab: /etc/fstab:2: Inappropriate file type or format
fstab: /etc/fstab:2: Inappropriate file type or format

/etc/fstab
# DeviceMountpoint  FStype  Options DumpPass#
/dev/gpt/Sea1-08  none swap 0   0
/dev/gpt/Sea1-18  / ufs rw  1   1
#/dev/gpt/Sea1-06 /home   ufs  rw 1  1

fsck -p produces

fstab: /etc/fstab:2: Inappropriate file type or format
/dev/gpt/Sea1-18: NO WRITE ACCESS
/dev/gpt/Sea1-18: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

I tried fsck /dev/gpt/Sea1-18 and fsck / but did no better.

Now what do I do?  I also ran fsck_ffs instead of just fsck.

Do I need to boot NetBSD and run fsck_ffs or fsck_ffs -f from there?

Tom

Re: What happen to mailing list archives?

[Baptiste Daroussin]

On Sat, Jun 05, 2021 at 05:43:01PM -0600, Warner Losh wrote:
> On Sat, Jun 5, 2021, 5:29 PM Steve Kargl 
> wrote:
> 
> > On Sun, Jun 06, 2021 at 01:04:46AM +0200, Michael Gmelin wrote:
> > >
> > > p.s. If you go to https://lists.freebsd.org/mailman/listinfo, click
> > FreeBSD-net and then "Archives from mailman’s time", you get to a list that
> > brings you to https://lists.freebsd.org/pipermail/freebsd-net/. So the
> > old archives are still reachable that way. (I still find the
> > docs.FreeBSD.org/mail page to be confusing).
> > >
> > >
> >
> > There isn't an "Archives from mailman's time" link on freebsd-numerics.
> >
> > Hundreds of emails from me are now gone or sufficiently hidden that
> > I cannot find them.  More importantly, Bruce Evans often replied
> > with reviews of libm patch's I sent the list.  Those reviews and
> > his detailed analysis of the libm code are now gone or sufficiently
> > hidded that I cannot find them.
> >
> 
> 
> Bapt was working on this stuff today. He said something about the archive
> regenerating with the new software on IRC..
> 
> Warner
> 
What has happended:
plan A: we migrated everything off mailman/pipermail seamlessly with redirection
and so on. We patched the new archiver to produce the same file names has
pipermail

Plan A worked fine up to a limit, there was plenty of hand edition in the past,
we we decided to move to plan B which is what is happening now.

Plan B: We keep a frozen version of the archives up to the migration date under
the pipermail directory and have the new archives created in the archives
directory.

All the pipermail archives have been restored as they were. The new archives
receives in their index a new link to point people to the pipermails archive if
looking for older archives.

this has been done a couple of hours ago (before Steve emails) during a window,
of ~ 10 hours, the mailing lists which slow traffic aka the one which didn't
received any email since the migration ended up with an empty "archives"
directory (aka a 404), a file with explanation and redirection to pipermail has
been installed there.

Some work is still needed for the mailing lists which has been transformed as
readonly, this will be done in the next couple of days

Bapt

FreeBSD service bug 256182 (was: What happen to mailing list archives?)

[Graham Perrin]

On 06/06/2021 00:28, Steve Kargl wrote:

Hundreds of emails from me are now gone or sufficiently hidden that
I cannot find them.  More importantly, Bruce Evans often replied
with reviews of libm patch's I sent the list.  Those reviews and
his detailed analysis of the libm code are now gone or sufficiently
hidded that I cannot find them.


256182 – lists.freebsd.org/pipermail/… redirections to 
lists.freebsd.org/archives/…: sometimes to the wrong content, sometimes 
not found (404)