Re: Zpool doesn't boot anymore after FreeBSD 12.1

[Cassiano Peixoto]

Ok, thanks. Please keep me posted.

On Thu, Oct 22, 2020 at 5:37 PM Toomas Soome  wrote:

>
>
> On 22. Oct 2020, at 23:29, Cassiano Peixoto 
> wrote:
>
>
> Hi Toomas,
>
> Thank you for this patch. Can I know when it will be MFCed? I'd like to
> try.
>
>
>
> MFC will take a bit because I need to bring it together with asize
> updates, so we would need to do a bit of cherry-picking and testing.
>
> rgds,
> toomas
>
>
>
>
> Hi!
>
> Please try 366951:) I think, it should get things better for you.
>
> rgds,
> toomas
>
> On Thu, Oct 22, 2020 at 3:04 PM Cassiano Peixoto <
> peixotocassi...@gmail.com> wrote:
>
>> Sergey,
>>
>> I agree with you. The best thing is to revert the commit on zfsloader.
>> Many people didn't realize this issue yet, but they will run into a big
>> problem soon.
>>
>> On Thu, Oct 22, 2020 at 2:41 PM Sergey V. Dyatko 
>> wrote:
>>
>>> On Thu, 22 Oct 2020 16:42:16 +0300
>>> Andriy Gapon  wrote:
>>>
>>> > On 22/10/2020 16:39, Cassiano Peixoto wrote:
>>> > > Hi Andriy,
>>> > >
>>> > > I've just tried copying my zfsloader from 11.2-STABLE (R350026) to
>>> FreeBSD
>>> > > 12.1 and 12.2 (STABLE) and fixed the issue.
>>> > >
>>> > > I also tried to use zfsloader of 11.3 but didn't work and the same
>>> issue
>>> > > happened.
>>> > >
>>> > > So it seems that something has changed on zfsloader after 11.2 that
>>> brings
>>> > > this issue.
>>> > >
>>> > > My question is: Should it be expected or is it a bug to be fixed?
>>> > >
>>> >
>>> > In my opinion it's a bug.
>>> > zfsloader should not require that disks must be partitioned.
>>> >
>>>
>>> +1
>>> That's why I have terribly outdated 13-CURRENT on bunch of servers and
>>> can't
>>> update them.
>>>
>>> Most of them look like this:
>>> [tiger@st25]:~>zpool status
>>>   pool: st25
>>>  state: ONLINE
>>>   scan: none requested
>>> config:
>>>
>>> NAMESTATE READ WRITE CKSUM
>>> st25   ONLINE   0 0 0
>>>   mirror-0  ONLINE   0 0 0
>>> ada0ONLINE   0 0 0
>>> ada1ONLINE   0 0 0
>>>   mirror-1  ONLINE   0 0 0
>>> ada2ONLINE   0 0 0
>>> ada3ONLINE   0 0 0
>>>   mirror-2  ONLINE   0 0 0
>>> ada4ONLINE   0 0 0
>>> ada5ONLINE   0 0 0
>>>   mirror-3  ONLINE   0 0 0
>>> ada6ONLINE   0 0 0
>>> ada7ONLINE   0 0 0
>>>
>>> errors: No known data errors
>>>
>>> They haven't separate boot device and have from 7 to 30+ Tb of data that
>>> I
>>> can't backup anywhere for re-install server with disk partitioning. Some
>>> time
>>> ago I managed to get aroud this reverting 2 commits (  r342151 + don't
>>> remember revision) but then there where some other improvements after
>>> which I
>>> lost the opportunity to revert this commits
>>>
>>> --
>>> wbr, Sergey
>>>
>>> ___
>>> freebsd-stable@freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org
>>> "
>>>
>>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Zpool doesn't boot anymore after FreeBSD 12.1

[Cassiano Peixoto]

Hi Toomas,

Thank you for this patch. Can I know when it will be MFCed? I'd like to try.


Hi!

Please try 366951:) I think, it should get things better for you.

rgds,
toomas

On Thu, Oct 22, 2020 at 3:04 PM Cassiano Peixoto 
wrote:

> Sergey,
>
> I agree with you. The best thing is to revert the commit on zfsloader.
> Many people didn't realize this issue yet, but they will run into a big
> problem soon.
>
> On Thu, Oct 22, 2020 at 2:41 PM Sergey V. Dyatko 
> wrote:
>
>> On Thu, 22 Oct 2020 16:42:16 +0300
>> Andriy Gapon  wrote:
>>
>> > On 22/10/2020 16:39, Cassiano Peixoto wrote:
>> > > Hi Andriy,
>> > >
>> > > I've just tried copying my zfsloader from 11.2-STABLE (R350026) to
>> FreeBSD
>> > > 12.1 and 12.2 (STABLE) and fixed the issue.
>> > >
>> > > I also tried to use zfsloader of 11.3 but didn't work and the same
>> issue
>> > > happened.
>> > >
>> > > So it seems that something has changed on zfsloader after 11.2 that
>> brings
>> > > this issue.
>> > >
>> > > My question is: Should it be expected or is it a bug to be fixed?
>> > >
>> >
>> > In my opinion it's a bug.
>> > zfsloader should not require that disks must be partitioned.
>> >
>>
>> +1
>> That's why I have terribly outdated 13-CURRENT on bunch of servers and
>> can't
>> update them.
>>
>> Most of them look like this:
>> [tiger@st25]:~>zpool status
>>   pool: st25
>>  state: ONLINE
>>   scan: none requested
>> config:
>>
>> NAMESTATE READ WRITE CKSUM
>> st25   ONLINE   0 0 0
>>   mirror-0  ONLINE   0 0 0
>> ada0ONLINE   0 0 0
>> ada1ONLINE   0 0 0
>>   mirror-1  ONLINE   0 0 0
>> ada2ONLINE   0 0 0
>> ada3ONLINE   0 0 0
>>   mirror-2  ONLINE   0 0 0
>> ada4ONLINE   0 0 0
>> ada5ONLINE   0 0 0
>>   mirror-3  ONLINE   0 0 0
>> ada6ONLINE   0 0 0
>> ada7ONLINE   0 0 0
>>
>> errors: No known data errors
>>
>> They haven't separate boot device and have from 7 to 30+ Tb of data that I
>> can't backup anywhere for re-install server with disk partitioning. Some
>> time
>> ago I managed to get aroud this reverting 2 commits (  r342151 + don't
>> remember revision) but then there where some other improvements after
>> which I
>> lost the opportunity to revert this commits
>>
>> --
>> wbr, Sergey
>>
>> ___
>> freebsd-stable@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Zpool doesn't boot anymore after FreeBSD 12.1

[Cassiano Peixoto]

Sergey,

I agree with you. The best thing is to revert the commit on zfsloader. Many
people didn't realize this issue yet, but they will run into a big problem
soon.

On Thu, Oct 22, 2020 at 2:41 PM Sergey V. Dyatko 
wrote:

> On Thu, 22 Oct 2020 16:42:16 +0300
> Andriy Gapon  wrote:
>
> > On 22/10/2020 16:39, Cassiano Peixoto wrote:
> > > Hi Andriy,
> > >
> > > I've just tried copying my zfsloader from 11.2-STABLE (R350026) to
> FreeBSD
> > > 12.1 and 12.2 (STABLE) and fixed the issue.
> > >
> > > I also tried to use zfsloader of 11.3 but didn't work and the same
> issue
> > > happened.
> > >
> > > So it seems that something has changed on zfsloader after 11.2 that
> brings
> > > this issue.
> > >
> > > My question is: Should it be expected or is it a bug to be fixed?
> > >
> >
> > In my opinion it's a bug.
> > zfsloader should not require that disks must be partitioned.
> >
>
> +1
> That's why I have terribly outdated 13-CURRENT on bunch of servers and
> can't
> update them.
>
> Most of them look like this:
> [tiger@st25]:~>zpool status
>   pool: st25
>  state: ONLINE
>   scan: none requested
> config:
>
> NAMESTATE READ WRITE CKSUM
> st25   ONLINE   0 0 0
>   mirror-0  ONLINE   0 0 0
> ada0ONLINE   0 0 0
> ada1ONLINE   0 0 0
>   mirror-1  ONLINE   0 0 0
> ada2ONLINE   0 0 0
> ada3ONLINE   0 0 0
>   mirror-2  ONLINE   0 0 0
> ada4ONLINE   0 0 0
> ada5ONLINE   0 0 0
>   mirror-3  ONLINE   0 0 0
> ada6ONLINE   0 0 0
> ada7ONLINE   0 0 0
>
> errors: No known data errors
>
> They haven't separate boot device and have from 7 to 30+ Tb of data that I
> can't backup anywhere for re-install server with disk partitioning. Some
> time
> ago I managed to get aroud this reverting 2 commits (  r342151 + don't
> remember revision) but then there where some other improvements after
> which I
> lost the opportunity to revert this commits
>
> --
> wbr, Sergey
>
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Zpool doesn't boot anymore after FreeBSD 12.1

[Cassiano Peixoto]

Hi Andriy,

I've just tried copying my zfsloader from 11.2-STABLE (R350026) to FreeBSD
12.1 and 12.2 (STABLE) and fixed the issue.

I also tried to use zfsloader of 11.3 but didn't work and the same issue
happened.

So it seems that something has changed on zfsloader after 11.2 that brings
this issue.

My question is: Should it be expected or is it a bug to be fixed?

Thanks.

On Thu, Oct 22, 2020 at 4:39 AM Andriy Gapon  wrote:

> On 21/10/2020 15:20, Cassiano Peixoto wrote:
> > Hi there,
> >
> > Anyone can help please? I've many servers with this same issue. Thanks
>
> Can you try to replace /boot/zfsloader with zfsloader from other FreeBSD
> versions?
> E.g., 12.0, 12.2-RC, 11.4, recent snapshot of the CURRENT?
>
> > On Fri, Oct 16, 2020 at 10:24 AM Cassiano Peixoto <
> peixotocassi...@gmail.com>
> > wrote:
> >
> >> Hi there,
> >>
> >> I have a FreeBSD 12.1-STABLE running on VMWARE with one disk. Then I
> added two more disks to expand my pool. BTW I already did it many time with
> no issues.
> >>
> >> I ran:
> >>
> >> # zpool status
> >>   pool: zroot
> >>  state: ONLINE
> >> status: Some supported features are not enabled on the pool. The pool
> can
> >>  still be used, but some features are unavailable.
> >> action: Enable all features using 'zpool upgrade'. Once this is done,
> >>  the pool may no longer be accessible by software that does not
> support
> >>  the features. See zpool-features(7) for details.
> >>   scan: none requested
> >> config:
> >>
> >>  NAME STATE READ WRITE CKSUM
> >>  zrootONLINE   0 0 0
> >>gpt/disk0  ONLINE   0 0 0
> >>
> >> errors: No known data errors
> >>
> >> # zpool add -f zroot da1
> >> # zpool add -f zroot da2
> >> # zpool status
> >>   pool: zroot
> >>  state: ONLINE
> >>   scan: none requested
> >> config:
> >>
> >>  NAME STATE READ WRITE CKSUM
> >>  zrootONLINE   0 0 0
> >>gpt/disk0  ONLINE   0 0 0
> >>da1ONLINE   0 0 0
> >>da2ONLINE   0 0 0
> >>
> >> errors: No known data errors
> >> # reboot
> >>
> >> Then my system doesn’t boot anymore, i got the following error:
> >>
> >> gptzfsboot: error 4 lba 2038346899
> >> gptzfsboot: error 4 lba 1361327267
> >> /boot/config: -Dh
> >>
> >> BTX loader 1.00  BTX version is 1.02
> >> Consoles: internal video/keyboard serial port
> >> BIOS drive A: is fd0
> >> BIOS drive C: is disk0
> >> BIOS drive D: is disk1
> >> BIOS drive E: is disk2
> >> BIOS drive F: is disk3
> >> BIOS drive G: is disk4
> >> BIOS drive H: is disk5
> >> ZFS: i/o error - all block copies unavailable
> >> ZFS: failed to read pool zroot directory object
> >> BIOS 638kB/3143616kB available memory
> >>
> >> FreeBSD/x86 bootstrap loader, Revision 1.1
> >> ERROR: cannot open /boot/lua/loader.lua: invalid argument.
> >>
> >> Type '?' for list of commands, 'help' for more datailed help.
> >> OK
> >>
> >> I can import my pool with no problems using the lived, but I could not
> fix it.
> >>
> >> Seems a bug after 12.1-STABLE. Please, anyone can take a look ok that?
> >>
> >> Thanks.
> >>
> >>
> >>
> >>
> > ___
> > freebsd-stable@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org
> "
> >
>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Zpool doesn't boot anymore after FreeBSD 12.1

[Cassiano Peixoto]

Thanks for the tip! I've fixed the issue following the following steps:

1) added two new disks with the same size: da3 and da4

2) Made a partition for both:
gpart create -s gpt da3
gpart create -s gpt da4
gpart add -t freebsd-zfs da3
gpart  add -t freebsd-zfs da4

3) replace both disks on pool
zpool replace zroot da2 da3p1
zpool replace zroot da3 da4p1

4) rebuild bootcode
gpart boocode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0

Done! I rebooted and everything is working again.

Thank you guys for the support.

On Wed, Oct 21, 2020 at 5:36 PM Walter Cramer  wrote:

> I very much doubt that there's any remotely sane way to re-partition da1 &
> da2 while they are in the pool.
>
> If you carefully edit the output of the 'gpart backup' command, you
> probably can use 'gpart restore' to partition da1 and da2.  Read the
> 'gpart' man page very carefully, if you aren't familiar with that.  Also,
> you'll probably want to install bootstrap code on da1 & da2 with 'gpart
> bootstrap'.
>
> -Walter
>
> On Wed, 21 Oct 2020, Cassiano Peixoto wrote:
>
> > Walter,
>
> Yes, gpt/disk0 is da0. I can do the partition backup booting from livecd.
> But is there a way to make the partition of da1 and da2 since both are
> already inserted on pool? I think it's not allowed...
>
> Thanks.
>
>
> On Wed, Oct 21, 2020 at 5:18 PM Walter Cramer  wrote:
>
> > My guess - there is a work-around or two, but you'll face a lot more
> > grief, long-term, if you don't do things the right way (aka do a bunch of
> > re-install work) now.
> >
> > I'd start with 'gpart backup da0' (guessing that gpt/disk0 is on da0), to
> > see how the original disk is partitioned.  Then duplicate that
> > partitioning on da1 and da2.
> >
> > -Walter
> >
> > On Wed, 21 Oct 2020, Cassiano Peixoto wrote:
> >
> > > Hi guys,
> >
> > Thank your for your answer.
> >
> > @Ricchard First of all I didn't have a chance to run zpool upgrade,
> because
> > after the system update reboot i ran into the issue.
> >
> > @Walter and @mike Regarding making a partition, I never see any
> > recommendation about this, I've been always using the entire disk on a
> pool
> > to expand it. Until FreeBSD 11.2 it worked fine.
> >
> > Is there a workaround for this or should I reinstall the entire pool?
> >
> > On Wed, Oct 21, 2020 at 4:45 PM mike tancsa  wrote:
> >
> > > Just a guess, Is your VM still trying to boot from whatever gpt/disk0
> is
> > > ? Or is it perhaps trying to boot from da1 or da2 which does not have
> > > boot info ?  Generally its not recommended to use the entire disk as
> > > part of a pool. Create a partition scheme first
> > >
> > > gpart create -s gpt da1
> > >
> > > gpart add -t freebsd-zfs da1
> > >
> > > then add da1p1 to the pool
> > >
> > > ---Mike
> > >
> > >
> > > On 10/21/2020 8:20 AM, Cassiano Peixoto wrote:
> > > > Hi there,
> > > >
> > > > Anyone can help please? I've many servers with this same issue.
> Thanks
> > > >
> > > > On Fri, Oct 16, 2020 at 10:24 AM Cassiano Peixoto <
> > > peixotocassi...@gmail.com>
> > > > wrote:
> > > >
> > > >> Hi there,
> > > >>
> > > >> I have a FreeBSD 12.1-STABLE running on VMWARE with one disk. Then I
> > > added two more disks to expand my pool. BTW I already did it many time
> > with
> > > no issues.
> > > >>
> > > >> I ran:
> > > >>
> > > >> # zpool status
> > > >>   pool: zroot
> > > >>  state: ONLINE
> > > >> status: Some supported features are not enabled on the pool. The
> pool
> > > can
> > > >>  still be used, but some features are unavailable.
> > > >> action: Enable all features using 'zpool upgrade'. Once this is
> done,
> > > >>  the pool may no longer be accessible by software that does not
> > > support
> > > >>  the features. See zpool-features(7) for details.
> > > >>   scan: none requested
> > > >> config:
> > > >>
> > > >>  NAME STATE READ WRITE CKSUM
> > > >>  zrootONLINE   0 0 0
> > > >>gpt/disk0  ONLINE   0 0 0
> > > >>
> > > >> errors: No known data errors
> > > >>
> > > >> # zpool add -f zroot da1
> > > >> # z

Re: Zpool doesn't boot anymore after FreeBSD 12.1

[Cassiano Peixoto]

Walter,

Yes, gpt/disk0 is da0. I can do the partition backup booting from livecd.
But is there a way to make the partition of da1 and da2 since both are
already inserted on pool? I think it's not allowed...

Thanks.


On Wed, Oct 21, 2020 at 5:18 PM Walter Cramer  wrote:

> My guess - there is a work-around or two, but you'll face a lot more
> grief, long-term, if you don't do things the right way (aka do a bunch of
> re-install work) now.
>
> I'd start with 'gpart backup da0' (guessing that gpt/disk0 is on da0), to
> see how the original disk is partitioned.  Then duplicate that
> partitioning on da1 and da2.
>
> -Walter
>
> On Wed, 21 Oct 2020, Cassiano Peixoto wrote:
>
> > Hi guys,
>
> Thank your for your answer.
>
> @Ricchard First of all I didn't have a chance to run zpool upgrade, because
> after the system update reboot i ran into the issue.
>
> @Walter and @mike Regarding making a partition, I never see any
> recommendation about this, I've been always using the entire disk on a pool
> to expand it. Until FreeBSD 11.2 it worked fine.
>
> Is there a workaround for this or should I reinstall the entire pool?
>
> On Wed, Oct 21, 2020 at 4:45 PM mike tancsa  wrote:
>
> > Just a guess, Is your VM still trying to boot from whatever gpt/disk0 is
> > ? Or is it perhaps trying to boot from da1 or da2 which does not have
> > boot info ?  Generally its not recommended to use the entire disk as
> > part of a pool. Create a partition scheme first
> >
> > gpart create -s gpt da1
> >
> > gpart add -t freebsd-zfs da1
> >
> > then add da1p1 to the pool
> >
> > ---Mike
> >
> >
> > On 10/21/2020 8:20 AM, Cassiano Peixoto wrote:
> > > Hi there,
> > >
> > > Anyone can help please? I've many servers with this same issue. Thanks
> > >
> > > On Fri, Oct 16, 2020 at 10:24 AM Cassiano Peixoto <
> > peixotocassi...@gmail.com>
> > > wrote:
> > >
> > >> Hi there,
> > >>
> > >> I have a FreeBSD 12.1-STABLE running on VMWARE with one disk. Then I
> > added two more disks to expand my pool. BTW I already did it many time
> with
> > no issues.
> > >>
> > >> I ran:
> > >>
> > >> # zpool status
> > >>   pool: zroot
> > >>  state: ONLINE
> > >> status: Some supported features are not enabled on the pool. The pool
> > can
> > >>  still be used, but some features are unavailable.
> > >> action: Enable all features using 'zpool upgrade'. Once this is done,
> > >>  the pool may no longer be accessible by software that does not
> > support
> > >>  the features. See zpool-features(7) for details.
> > >>   scan: none requested
> > >> config:
> > >>
> > >>  NAME STATE READ WRITE CKSUM
> > >>  zrootONLINE   0 0 0
> > >>gpt/disk0  ONLINE   0 0 0
> > >>
> > >> errors: No known data errors
> > >>
> > >> # zpool add -f zroot da1
> > >> # zpool add -f zroot da2
> > >> # zpool status
> > >>   pool: zroot
> > >>  state: ONLINE
> > >>   scan: none requested
> > >> config:
> > >>
> > >>  NAME STATE READ WRITE CKSUM
> > >>  zrootONLINE   0 0 0
> > >>gpt/disk0  ONLINE   0 0 0
> > >>da1ONLINE   0 0 0
> > >>da2ONLINE   0 0 0
> > >>
> > >> errors: No known data errors
> > >> # reboot
> > >>
> > >> Then my system doesn’t boot anymore, i got the following error:
> > >>
> > >> gptzfsboot: error 4 lba 2038346899
> > >> gptzfsboot: error 4 lba 1361327267
> > >> /boot/config: -Dh
> > >>
> > >> BTX loader 1.00  BTX version is 1.02
> > >> Consoles: internal video/keyboard serial port
> > >> BIOS drive A: is fd0
> > >> BIOS drive C: is disk0
> > >> BIOS drive D: is disk1
> > >> BIOS drive E: is disk2
> > >> BIOS drive F: is disk3
> > >> BIOS drive G: is disk4
> > >> BIOS drive H: is disk5
> > >> ZFS: i/o error - all block copies unavailable
> > >> ZFS: failed to read pool zroot directory object
> > >> BIOS 638kB/3143616kB available memory
> > >>
> > >> FreeBSD/x86 bootstrap loader, Revision 1.1

Re: Zpool doesn't boot anymore after FreeBSD 12.1

[Cassiano Peixoto]

Hi guys,

Thank your for your answer.

@Ricchard First of all I didn't have a chance to run zpool upgrade, because
after the system update reboot i ran into the issue.

@Walter and @mike Regarding making a partition, I never see any
recommendation about this, I've been always using the entire disk on a pool
to expand it. Until FreeBSD 11.2 it worked fine.

Is there a workaround for this or should I reinstall the entire pool?

On Wed, Oct 21, 2020 at 4:45 PM mike tancsa  wrote:

> Just a guess, Is your VM still trying to boot from whatever gpt/disk0 is
> ? Or is it perhaps trying to boot from da1 or da2 which does not have
> boot info ?  Generally its not recommended to use the entire disk as
> part of a pool. Create a partition scheme first
>
> gpart create -s gpt da1
>
> gpart add -t freebsd-zfs da1
>
> then add da1p1 to the pool
>
> ---Mike
>
>
> On 10/21/2020 8:20 AM, Cassiano Peixoto wrote:
> > Hi there,
> >
> > Anyone can help please? I've many servers with this same issue. Thanks
> >
> > On Fri, Oct 16, 2020 at 10:24 AM Cassiano Peixoto <
> peixotocassi...@gmail.com>
> > wrote:
> >
> >> Hi there,
> >>
> >> I have a FreeBSD 12.1-STABLE running on VMWARE with one disk. Then I
> added two more disks to expand my pool. BTW I already did it many time with
> no issues.
> >>
> >> I ran:
> >>
> >> # zpool status
> >>   pool: zroot
> >>  state: ONLINE
> >> status: Some supported features are not enabled on the pool. The pool
> can
> >>  still be used, but some features are unavailable.
> >> action: Enable all features using 'zpool upgrade'. Once this is done,
> >>  the pool may no longer be accessible by software that does not
> support
> >>  the features. See zpool-features(7) for details.
> >>   scan: none requested
> >> config:
> >>
> >>  NAME STATE READ WRITE CKSUM
> >>  zrootONLINE   0 0 0
> >>gpt/disk0  ONLINE   0 0 0
> >>
> >> errors: No known data errors
> >>
> >> # zpool add -f zroot da1
> >> # zpool add -f zroot da2
> >> # zpool status
> >>   pool: zroot
> >>  state: ONLINE
> >>   scan: none requested
> >> config:
> >>
> >>  NAME STATE READ WRITE CKSUM
> >>  zrootONLINE   0 0 0
> >>gpt/disk0  ONLINE   0 0 0
> >>da1ONLINE   0 0 0
> >>da2ONLINE   0 0 0
> >>
> >> errors: No known data errors
> >> # reboot
> >>
> >> Then my system doesn’t boot anymore, i got the following error:
> >>
> >> gptzfsboot: error 4 lba 2038346899
> >> gptzfsboot: error 4 lba 1361327267
> >> /boot/config: -Dh
> >>
> >> BTX loader 1.00  BTX version is 1.02
> >> Consoles: internal video/keyboard serial port
> >> BIOS drive A: is fd0
> >> BIOS drive C: is disk0
> >> BIOS drive D: is disk1
> >> BIOS drive E: is disk2
> >> BIOS drive F: is disk3
> >> BIOS drive G: is disk4
> >> BIOS drive H: is disk5
> >> ZFS: i/o error - all block copies unavailable
> >> ZFS: failed to read pool zroot directory object
> >> BIOS 638kB/3143616kB available memory
> >>
> >> FreeBSD/x86 bootstrap loader, Revision 1.1
> >> ERROR: cannot open /boot/lua/loader.lua: invalid argument.
> >>
> >> Type '?' for list of commands, 'help' for more datailed help.
> >> OK
> >>
> >> I can import my pool with no problems using the lived, but I could not
> fix it.
> >>
> >> Seems a bug after 12.1-STABLE. Please, anyone can take a look ok that?
> >>
> >> Thanks.
> >>
> >>
> >>
> >>
> > ___
> > freebsd-stable@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org
> "
> >
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Zpool doesn't boot anymore after FreeBSD 12.1

[Cassiano Peixoto]

Hi there,

Anyone can help please? I've many servers with this same issue. Thanks

On Fri, Oct 16, 2020 at 10:24 AM Cassiano Peixoto 
wrote:

> Hi there,
>
> I have a FreeBSD 12.1-STABLE running on VMWARE with one disk. Then I added 
> two more disks to expand my pool. BTW I already did it many time with no 
> issues.
>
> I ran:
>
> # zpool status
>   pool: zroot
>  state: ONLINE
> status: Some supported features are not enabled on the pool. The pool can
>   still be used, but some features are unavailable.
> action: Enable all features using 'zpool upgrade'. Once this is done,
>   the pool may no longer be accessible by software that does not support
>   the features. See zpool-features(7) for details.
>   scan: none requested
> config:
>
>   NAME STATE READ WRITE CKSUM
>   zrootONLINE   0 0 0
> gpt/disk0  ONLINE   0 0 0
>
> errors: No known data errors
>
> # zpool add -f zroot da1
> # zpool add -f zroot da2
> # zpool status
>   pool: zroot
>  state: ONLINE
>   scan: none requested
> config:
>
>   NAME STATE READ WRITE CKSUM
>   zrootONLINE   0 0 0
> gpt/disk0  ONLINE   0 0 0
> da1ONLINE   0 0 0
> da2ONLINE   0 0 0
>
> errors: No known data errors
> # reboot
>
> Then my system doesn’t boot anymore, i got the following error:
>
> gptzfsboot: error 4 lba 2038346899
> gptzfsboot: error 4 lba 1361327267
> /boot/config: -Dh
>
> BTX loader 1.00  BTX version is 1.02
> Consoles: internal video/keyboard serial port
> BIOS drive A: is fd0
> BIOS drive C: is disk0
> BIOS drive D: is disk1
> BIOS drive E: is disk2
> BIOS drive F: is disk3
> BIOS drive G: is disk4
> BIOS drive H: is disk5
> ZFS: i/o error - all block copies unavailable
> ZFS: failed to read pool zroot directory object
> BIOS 638kB/3143616kB available memory
>
> FreeBSD/x86 bootstrap loader, Revision 1.1
> ERROR: cannot open /boot/lua/loader.lua: invalid argument.
>
> Type '?' for list of commands, 'help' for more datailed help.
> OK
>
> I can import my pool with no problems using the lived, but I could not fix it.
>
> Seems a bug after 12.1-STABLE. Please, anyone can take a look ok that?
>
> Thanks.
>
>
>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Zpool doesn't boot anymore after FreeBSD 12.1

[Cassiano Peixoto]

Hi there,

I have a FreeBSD 12.1-STABLE running on VMWARE with one disk. Then I
added two more disks to expand my pool. BTW I already did it many time
with no issues.

I ran:

# zpool status
  pool: zroot
 state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(7) for details.
  scan: none requested
config:

NAME STATE READ WRITE CKSUM
zrootONLINE   0 0 0
  gpt/disk0  ONLINE   0 0 0

errors: No known data errors

# zpool add -f zroot da1
# zpool add -f zroot da2
# zpool status
  pool: zroot
 state: ONLINE
  scan: none requested
config:

NAME STATE READ WRITE CKSUM
zrootONLINE   0 0 0
  gpt/disk0  ONLINE   0 0 0
  da1ONLINE   0 0 0
  da2ONLINE   0 0 0

errors: No known data errors
# reboot

Then my system doesn’t boot anymore, i got the following error:

gptzfsboot: error 4 lba 2038346899
gptzfsboot: error 4 lba 1361327267
/boot/config: -Dh

BTX loader 1.00  BTX version is 1.02
Consoles: internal video/keyboard serial port
BIOS drive A: is fd0
BIOS drive C: is disk0
BIOS drive D: is disk1
BIOS drive E: is disk2
BIOS drive F: is disk3
BIOS drive G: is disk4
BIOS drive H: is disk5
ZFS: i/o error - all block copies unavailable
ZFS: failed to read pool zroot directory object
BIOS 638kB/3143616kB available memory

FreeBSD/x86 bootstrap loader, Revision 1.1
ERROR: cannot open /boot/lua/loader.lua: invalid argument.

Type '?' for list of commands, 'help' for more datailed help.
OK

I can import my pool with no problems using the lived, but I could not fix it.

Seems a bug after 12.1-STABLE. Please, anyone can take a look ok that?

Thanks.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: lightly loaded system eats swap space

[Cassiano Peixoto]

Hi,

I have the very same issue on many servers. Mainly on mail servers running
qmail+spamassassin+clamav. I've tuned some variables on loader.conf:

vfs.zfs.vdev.cache.size="2G"
vfs.zfs.arc_min="61440"
vfs.zfs.arc_max="491520"

But after some days, it begins eating swap and the system comes very very
slow then I need to reboot it.

My system config is:

FreeBSD 11.1-STABLE #5 r321625M: Thu Sep 21 16:01:56 -03 2017
r...@mail.com:/usr/obj/usr/src/sys/MAIL amd64
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM
4.0.0)
VT(vga): resolution 640x480
CPU: Intel(R) Atom(TM) CPU  C2518  @ 1.74GHz (1750.04-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x406d8  Family=0x6  Model=0x4d  Stepping=8

Features=0xbfebfbff

Features2=0x43d8e3bf
  AMD Features=0x28100800
  AMD Features2=0x101
  Structured Extended Features=0x2282
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 8589934592 (8192 MB)
avail memory = 8213245952 (7832 MB)

It's configured with 4GB of swap. Let me know if I can help with any other
information.

Thanks.


On Tue, Jun 19, 2018 at 2:29 PM, Jeremy Chadwick  wrote:

> (I am not subscribed to -stable, so please CC me, though I doubt I can
> help in any way/shape/form past this Email)
>
> Not the first time this has come up -- and every time it has, all that's
> heard is crickets in the threads.  Recent proof:
>
> https://lists.freebsd.org/pipermail/freebsd-stable/2018-April/088727.html
> https://lists.freebsd.org/pipermail/freebsd-stable/2018-April/088728.html
> https://lists.freebsd.org/pipermail/freebsd-stable/2018-June/089094.html
>
> I sent private mail to Peter Jeremy about his issue.  I will not
> disclose that Email here.  However, I will disclose the commits I
> included in said Email that have touched ZFS ARC-related code:
>
> http://www.freshbsd.org/commit/freebsd/r332785
> http://www.freshbsd.org/commit/freebsd/r332552
> http://www.freshbsd.org/commit/freebsd/r332540 (may help give insights)
> http://www.freshbsd.org/commit/freebsd/r330061
> http://www.freshbsd.org/commit/freebsd/r328235
> http://www.freshbsd.org/commit/freebsd/r327491
> http://www.freshbsd.org/commit/freebsd/r326619
> http://www.freshbsd.org/commit/freebsd/r326427 (quota-related, maybe
> irrelevant)
> http://www.freshbsd.org/commit/freebsd/r323667
>
> In short (and nebulous as hell; sorry, I cannot be more specific given
> the nature of the problem): there have been changes about ZFS's memory
> allocation/releasing decision-making scheme compared to ZFS on "older"
> FreeBSD (i.e. earlier 11.x, and definitely 10.x and 9.x).
>
> Recommendations like "limit your ARC" are nothing new in FreeBSD, but
> are still ridiculous kludges: tech-lists' system clearly has 105GB MRU
> (MRU = most recently used) in ARC, meaning there is memory that can be
> released back to the rest of the OS for general use (re: memory
> contention/pressure situation), but the OS is choosing to use swap
> instead, eventually exhausting it.  That logic sounds broken, IMO.  (And
> yes I did notice the size of bhyve process)
>
> ZFS-related kernel folks need to be involved in this conversation.  For
> whatever reason, in the past several years, related committers are no
> longer participating in these type of discussions.  The opposite was
> true back in the 7.x to 9.x days.  The answers have to come from them.
> I don't know, today, a) how they prefer these problems get reported to
> them, or b) what exact information they want that can help narrow it
> down (tech-lists' provided data is, IMO, good and par for the course).
>
> --
> | Jeremy Chadwick   j...@koitsu.org |
> | UNIX Systems Administratorhttp://jdc.koitsu.org/ |
> | Making life hard for others since 1977. PGP 4BD6C0CB |
>
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Denverton CPU on FreeBSD

[Cassiano Peixoto]

Hi Bob,

Yes I've tried this configuration with no success as well. :(

On Tue, Nov 7, 2017 at 2:28 PM, Bob Bishop <r...@gid.co.uk> wrote:

> Hi,
>
> > On 7 Nov 2017, at 16:12, Cassiano Peixoto <peixotocassi...@gmail.com>
> wrote:
> >
> > Hi guys,
> >
> > I'm backing to this thread because I had no success yet. There is an
> issue
> > with console boot on Intel Denverton. I've followed the instruction
> bellow:
> >
> > https://www.freebsd.org/doc/handbook/serialconsole-setup.html
> >
> > I tried using an IPMI card and worked fine.
> >
> > I don't know who is the maintainer for console code to get in touch. Can
> > some developer work on this issue? I can help making any test needed.
> >
> > Thank you.
> >
> > On Wed, Aug 16, 2017 at 5:32 PM, Cassiano Peixoto <
> peixotocassi...@gmail.com
> >> wrote:
> >
> >> Hi there,
> >>
> >> Is someone playing with Denverton CPU On FreeBSD?
> >>
> >> I'm trying to use serial console on FreeBSD with Denverton CPU but
> doesn't
> >> work.
> >>
> >> I can see the boot process but it stops and I do not have the login
> >> prompt. My keyboard doesn't answer as well.
>
> Have you set /etc/ttys entry for the serial port appropriately?
> https://www.freebsd.org/doc/handbook/term.html#term-config
>
> >> I tried it with FreeBSD 10, 11 and 12-CURRENT. Same configuration is
> >> working with Rangeley CPU.
>
> Maybe BIOS initialises the serial port differently?
>
> >> Any help is welcome.
> >>
> >> Thanks.
> >>
> > ___
> > freebsd-stable@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org
> "
> >
>
>
> --
> Bob Bishop   t: +44 (0)118 940 1243
> r...@gid.co.uk m: +44 (0)783 626 4518
>
>
>
>
>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Denverton CPU on FreeBSD

[Cassiano Peixoto]

Hi guys,

I'm backing to this thread because I had no success yet. There is an issue
with console boot on Intel Denverton. I've followed the instruction bellow:

https://www.freebsd.org/doc/handbook/serialconsole-setup.html

I tried using an IPMI card and worked fine.

I don't know who is the maintainer for console code to get in touch. Can
some developer work on this issue? I can help making any test needed.

Thank you.

On Wed, Aug 16, 2017 at 5:32 PM, Cassiano Peixoto <peixotocassi...@gmail.com
> wrote:

> Hi there,
>
> Is someone playing with Denverton CPU On FreeBSD?
>
> I'm trying to use serial console on FreeBSD with Denverton CPU but doesn't
> work.
>
> I can see the boot process but it stops and I do not have the login
> prompt. My keyboard doesn't answer as well.
>
> I tried it with FreeBSD 10, 11 and 12-CURRENT. Same configuration is
> working with Rangeley CPU.
>
> Any help is welcome.
>
> Thanks.
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg issue after FreeBSD 11 upgrade

[Cassiano Peixoto]

Hi Baptiste,

Sorry to bother you. Did you have some time to work on this thread?

Thanks.

On Wed, Aug 30, 2017 at 12:46 PM, Cassiano Peixoto <
peixotocassi...@gmail.com> wrote:

> Thank you for your support Baptiste, I really appreciate that.
>
> As same as HANDLE_RC_SCRIPTS option the new one should be handled
> carefully.
>
> Please keep us posted when it's ready.
>
>
> On Wednesday, August 30, 2017, Baptiste Daroussin <b...@freebsd.org>
> wrote:
>
>> On Wed, Aug 30, 2017 at 10:07:51AM -0300, Cassiano Peixoto wrote:
>> > Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal
>> > with when I need to restart a service without upgrading? Reaper
>> > functionnality is a trouble for many administrators who made meta ports
>> to
>> > manage their servers. I really think it could be a option to be
>> > enabled/disabled. Can you see this possibility?
>> >
>>
>> Yes I could add an option to disable the reaper functionnality (and will
>> probably to unblock such use case as soon as I have time to do it.)
>>
>> However I still think this is not the right idea :) and a better one
>> could be
>> found
>>
>> Bapt
>>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg issue after FreeBSD 11 upgrade

[Cassiano Peixoto]

Thank you for your support Baptiste, I really appreciate that.

As same as HANDLE_RC_SCRIPTS option the new one should be handled carefully.

Please keep us posted when it's ready.

On Wednesday, August 30, 2017, Baptiste Daroussin <b...@freebsd.org> wrote:

> On Wed, Aug 30, 2017 at 10:07:51AM -0300, Cassiano Peixoto wrote:
> > Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal
> > with when I need to restart a service without upgrading? Reaper
> > functionnality is a trouble for many administrators who made meta ports
> to
> > manage their servers. I really think it could be a option to be
> > enabled/disabled. Can you see this possibility?
> >
>
> Yes I could add an option to disable the reaper functionnality (and will
> probably to unblock such use case as soon as I have time to do it.)
>
> However I still think this is not the right idea :) and a better one could
> be
> found
>
> Bapt
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg issue after FreeBSD 11 upgrade

[Cassiano Peixoto]

Hi Franco,

Thank you. You know what I'm suffering. As I said in my last email I think
it would be an option to enable/disable. I just upgraded my customers
servers to FreeBSD 11 and I just realized it. I think when more admins who
maintain this kind of port (needing to restart services), as soon as they
migrate they will face the same problem.

On Wed, Aug 30, 2017 at 10:01 AM, Franco Fichtner <fra...@lastsummer.de>
wrote:

> Hi Cassiano,
>
> > On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto <peixotocassi...@gmail.com>
> wrote:
> >
> > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only.
>
> It was a later 10.x change as far as I know.
>
> > Is there some flag to disable it? Or some hack that I could do?
>
> No.  At OPNsense we use a patch to revert the behaviour.
>
> https://github.com/opnsense/ports/blob/master/ports-mgmt/
> pkg/files/patch-libpkg_scripts.c
>
>
> Cheers,
> Franco
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg issue after FreeBSD 11 upgrade

[Cassiano Peixoto]

Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal
with when I need to restart a service without upgrading? Reaper
functionnality is a trouble for many administrators who made meta ports to
manage their servers. I really think it could be a option to be
enabled/disabled. Can you see this possibility?

Thanks.

On Wed, Aug 30, 2017 at 9:59 AM, Baptiste Daroussin <b...@freebsd.org>
wrote:

> On Wed, Aug 30, 2017 at 09:55:22AM -0300, Cassiano Peixoto wrote:
> > Hi Baptiste,
> >
> > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only.
>
> It only worked on FreeBSD 10 prior to 10.2, the reaper functionnality in
> freebsd
> kernel appeared in 10.2
> >
> > Cron is just an example, I manage more than 50 FreeBSD servers, and I've
> > been using ports for years to update some configs and restart the service
> > on all of them. Many times I need to change nginx config, ldap, etc. I
> just
> > need to restart the service.
>
> HANDLE_RC_SCRIPTS=true in your pkg.conf and pkg will automatically restart
> anything rc script provide once the package containing it is upgrading.
>
> This is off by default because in many cases it is dangerous (database
> upgrades,
> dovecot like things upgrade etc). But if you know what you are doing it
> does the
> job.
>
> Best regards,
> Bapt
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg issue after FreeBSD 11 upgrade

[Cassiano Peixoto]

Hi Baptiste,

Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only.

Cron is just an example, I manage more than 50 FreeBSD servers, and I've
been using ports for years to update some configs and restart the service
on all of them. Many times I need to change nginx config, ldap, etc. I just
need to restart the service.

Is there some flag to disable it? Or some hack that I could do?

Thanks.



On Wed, Aug 30, 2017 at 9:48 AM, Baptiste Daroussin <b...@freebsd.org>
wrote:

> On Wed, Aug 30, 2017 at 09:00:55AM -0300, Cassiano Peixoto wrote:
> > Hi Matthew,
> >
> > Sorry back to this subject. But I really need to restart services with a
> > port. I'm quite sure there is a bug with pkg and FreeBSD 11.
> >
> > I made a simple port to restart cron service:
>
> It is not a bug, it is by design, pkg becomes the reaper of the scripts it
> runs
> and kills everything once the script is executed.
>
> btw if you install crontab in cron.d you do not need to restart the
> service,
> cron will figure out itself and reload what it needed.
>
> Bapt
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: pkg issue after FreeBSD 11 upgrade

[Cassiano Peixoto]

Hi Matthew,

Sorry back to this subject. But I really need to restart services with a
port. I'm quite sure there is a bug with pkg and FreeBSD 11.

I made a simple port to restart cron service:

# $FreeBSD$
PORTNAME=   ze
PORTVERSION=1.0
CATEGORIES= custom
MASTER_SITES=   #
DISTFILES=  #
EXTRACT_ONLY=   # NONE

MAINTAINER= peixotocassi...@gmail.com
COMMENT=ze port

#NO_MTREE=  yes



SUB_FILES=  pkg-install



NO_BUILD=   yes

NO_WRKSUBDIR=   yes



do-install:

mkdir -p ${STAGEDIR}${DATADIR}

@${CP} -r ${FILESDIR}/versions ${STAGEDIR}${DATADIR}/



post-install:

${SH} ${PKGINSTALL} ${PKGNAME} POST-INSTALL


.include 

Here is my pkg-install to restart cron service:

#!/bin/sh

if [ $2 = "POST-INSTALL" ]; then

  service cron restart

fi

Here is the output when I install the port:

root@kkk:~ # service cron start
cron already running?  (pid=2287).

root@kkk:~ # pkg install ze
Updating Custom repository catalogue...
Fetching meta.txz: 100%560 B   0.6kB/s00:01
Fetching packagesite.txz: 100%  122 KiB  62.6kB/s00:02
Processing entries: 100%
Custom repository update completed. 427 packages processed.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
ze: 1.0

Number of packages to be installed: 1

672 B to be downloaded.
[1/1] Fetching ze-1.0.txz: 100%672 B   0.7kB/s00:01
Checking integrity... done (0 conflicting)
[1/1] Installing ze-1.0...
+ set -- ze-1.0 PRE-INSTALL
+ [ PRE-INSTALL '=' POST-INSTALL ]
Extracting ze-1.0: 100%
+ set -- ze-1.0 POST-INSTALL
+ [ POST-INSTALL '=' POST-INSTALL ]
+ service cron restart
Stopping cron.
Waiting for PIDS: 2287.
Starting cron.

root@kkk:~ # ps ax | grep cron
2320  1  S+ 0:00.00 grep cron

As you can see the cron has stopped but hasn't started.

But If I install the same port with traditional ports approach it works,
see:

root@kkk: /usr/ports/custom/ze/# ps ax | grep cron
 1280  -  Is   0:00.97 /usr/sbin/cron -s

root@kkk: /usr/ports/custom/ze# make install
===>   ze-1.1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by ze-1.1 for building
===>  Extracting for ze-1.1
===>  Patching for ze-1.1
===>  Configuring for ze-1.1
===>  Staging for ze-1.1
===>   Generating temporary packing list
mkdir -p /usr/ports/custom/ze/work/stage/usr/local/share/ze
/bin/sh /usr/ports/custom/ze/work/pkg-install ze-1.1 POST-INSTALL
> Compressing man pages (compress-man)
===>  Installing for ze-1.1
===>  Checking if ze already installed
Stopping cron.
Waiting for PIDS: 1280.
Starting cron.
===>   Registering installation for ze-1.1
Installing ze-1.1...

root@kkk: /usr/ports/custom/ze# ps ax | grep cron
37527  -  Ss   0:00.00 /usr/sbin/cron -s

Thanks for your help.



On Fri, Aug 11, 2017 at 1:45 PM, Cassiano Peixoto <peixotocassi...@gmail.com
> wrote:

> Hi Matthew,
>
> Thanks for your answer. Slapd is just an example, it happens with any
> application like apache, mysql, dovecot and others.
>
> I can see the process is running and up, and it dies after pkg process has
> finished. Looks like pkg is killing any application related to its thread.
>
> I know it's not the best approach, but used to work on FreeBSD 10.
>
> Anyway, I'll change my script to restart services out of pkg process.
>
> Thanks.
>
> On Fri, Aug 11, 2017 at 5:09 AM, Matthew Seaman <matt...@freebsd.org>
> wrote:
>
>> On 10/08/2017 22:05, Cassiano Peixoto wrote:
>> > I ran into an issue after FreeBSD 11 upgrade. I have some meta ports
>> that
>> > starts services like slapd.
>> >
>> > Its has been working fine on 10-STABLE. But after FreeBSD
>> > 11-STABLE r321625M upgrade it stopped working.
>> >
>> > Here is a simple example of my pkg-install.in script:
>> >
>> > #!/bin/sh
>> > /usr/local/etc/rc.d/slapd stop
>> > /usr/local/etc/rc.d/slapd start
>> >
>> > I can see its executing while upgrading a package:
>> >
>> > Stopping slapd.
>> > Waiting for PIDS: 13875.
>> > Starting slapd.
>> >
>> > But looking if the process is running, it's not:
>> >
>> > # ps ax | grep slapd
>> > 14164  0  S+ 0:00.00 grep slapd
>> >
>> > Then I manually run the rc.d script and the service starts:
>> >
>> > # /usr/local/etc/rc.d/slapd restart
>> > slapd not running? (check /var/run/openldap/slapd.pid).
>> > Starting slapd.
>> >
>> > So my question is: something has changed on FreeBSD 11 not allowing this
>> > kind of execution?
>> >
>> > BTW, I'm using pkg 1.10.1 and my ports collection is as same as I was
>> using
>> &g

Denverton CPU on FreeBSD

[Cassiano Peixoto]

Hi there,

Is someone playing with Denverton CPU On FreeBSD?

I'm trying to use serial console on FreeBSD with Denverton CPU but doesn't
work.

I can see the boot process but it stops and I do not have the login prompt.
My keyboard doesn't answer as well.

I tried it with FreeBSD 10, 11 and 12-CURRENT. Same configuration is
working with Rangeley CPU.

Any help is welcome.

Thanks.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Support for X553 (Denverton) Ethernet devices

[Cassiano Peixoto]

Hi Jeb,

Thank you. Keep me posted to try as soon as it's available.

On Tue, Jul 11, 2017 at 1:42 PM, Cramer, Jeb J <jeb.j.cra...@intel.com>
wrote:

> Hi Cassiano,
>
> We’ve added support to HEAD and are creating the patch to apply to
> 11-STABLE as this moment.  It should be posted today or maybe tomorrow at
> the latest.
>
> Thanks,
> -Jeb
>
> From: Cassiano Peixoto [mailto:peixotocassi...@gmail.com]
> Sent: Tuesday, July 11, 2017 6:52 AM
> To: freebsd-stable@freebsd.org; freebsd-...@freebsd.org
> Cc: e...@freebsd.org; Cramer, Jeb J <jeb.j.cra...@intel.com>; Pieper,
> Jeffrey E <jeffrey.e.pie...@intel.com>
> Subject: Support for X553 (Denverton) Ethernet devices
>
> Hi guys,
>
> I've been playing with Denverton, but I realized that ethernet devices
> wasn't recognized.
>
> I found this commit here enabling X553 support on 10-STABLE:
> http://freshbsd.org/commit/freebsd/r315333
> https://reviews.freebsd.org/D9310
>
> I tested on 10-STABLE and worked fined. But on 11-STABLE it didn't find
> the ethernet interfaces.
>
> Seems IFLIB support is needed, anyway I enabled support in kernel but
> nothing has changed.
>
> Am I missing something here or support to X553 wasn't added to 11-STABLE?
>
> Thanks.
> ___
> freebsd-...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Support for X553 (Denverton) Ethernet devices

[Cassiano Peixoto]

Hi guys,

I've been playing with Denverton, but I realized that ethernet devices
wasn't recognized.

I found this commit here enabling X553 support on 10-STABLE:
http://freshbsd.org/commit/freebsd/r315333
https://reviews.freebsd.org/D9310

I tested on 10-STABLE and worked fined. But on 11-STABLE it didn't find the
ethernet interfaces.

Seems IFLIB support is needed, anyway I enabled support in kernel but
nothing has changed.

Am I missing something here or support to X553 wasn't added to 11-STABLE?

Thanks.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0-RELEASE Status Update

[Cassiano Peixoto]

Looks we have some import issues to be fixed before 11-RELEASE. I have
another one that nobody cares:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257
and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212413

It's affecting ALTQ users on both FreeBSD 11 and 10.3, the system just
crash.

IMHO would be better to release a stable product instead of keep the
schedule.


On Fri, Oct 7, 2016 at 8:32 AM, Alexander Shitov  wrote:

> Op 06/10/2016 om 22:18 schreef Glen Barber:
> > As many of you are aware, 11.0-RELEASE needed to be rebuilt to address
> > several issues that were discovered after the release was built. Extra
> > caution is being taken in testing the rebuilt releases, so at present,
> > the final release announcement is planned for Monday, October 10.
> >
> > Thank you for your patience in waiting for 11.0-RELEASE.
> >
> > Glen > On behalf of: re@ >
>
> Is fix for Hyper-V bug "virtual disk being detached from the bus"
> (https://reviews.freebsd.org/D7693)  included in final build?
> PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212721
>
> It will be big disappointment if 11.0-RELEASE will became incompatible
> with Hyper-V.
>
> ---
> Best Regards,
> Alexander
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: zfs crash under load on 11-Prerelease r305056

[Cassiano Peixoto]

Hi,

I've the same issue here with my ZFS server. I've updated from 10.3-STABLE
to 11-PRERELEASE. Then after some time my server just crash.

Then i tried to update again using another svn server. After many tries
(because my server has been crashed all the time) i got RC2. But same issue
still happening.

It's not simple to reproduce, but the crashs seems be random after some
time. Some time it happened when i was running buildworld, others on
installworld, or even a simple cat on some log file.

It reminds me a bug about a month ago on RELENG11 mentioned by Glen Barber
where the system crashs all the time.

Let me know if i can help any way.

Thanks


>
> *From:* Volodymyr Kostyrko 
> *Date:* 3 de setembro de 2016 06:51:21 BRT
> *To:* freebsd-stable@freebsd.org
> *Subject:* *zfs crash under load on 11-Prerelease r305056*
>
> Hi all.
>
> Got one host without keyboard so can't dump it.
>
> Screenshot: http://limb0.b1t.name/incoming/IMG_20160903_120545.jpg
>
> This is MINIMAL kernel with minor additions.
>
> --
> Sphinx of black quartz judge my vow.
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>
>
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Issue with /boot/menu.rc.local after 10.2 update

[Cassiano Peixoto]

I just found out the problem. I don't know who added the following phrase
to /boot/menu-commands.4th:

only forth definitions

Line 31 and 354. It just broke /boot/menu.rc.local as i said before. After
removing that everything worked again. Hope it helps someone else. I'm
going to open a PR anyway.

Thanks.

On Tue, Aug 18, 2015 at 11:13 AM, Cassiano Peixoto 
peixotocassi...@gmail.com wrote:

 Hi guys,

 I've been using /boot/menu.rc.local for years to my custom menu option.
 But after 10.2 update, it's not working anymore. I always get the message
 toggle_menuitem not found on beastie menu.

 Here is my /boot/menu.rc.local:

 set optionsmenu_init[7]=init_console
 set optionsmenu_caption[7]=[C]onsole. Off
 set optionstoggled_text[7]=[C]onsole. On
 set optionsmenu_command[7]=toggle_console
 set optionsmenu_keycode[7]=118
 set optionsansi_caption[7]=^[[1mC^[[37monsole. ^[[34;1mOff^[[37m
 set optionstoggled_ansi[7]=^[[1mC^[[37monsole. ^[[32;7mOn^[[0;37m

 \
 \ Console Boot
 \

 : console_enabled? ( -- flag )
 s boot_single getenv -1  dup if
 drop ( c-addr flag -- flag )
 then
 ;

 : console_enable ( -- )
 s set console=comconsole,vidconsole evaluate
 ;

 : console_disable ( -- )
 s set console=vidconsole,comconsole evaluate
 ;

 : toggle_console ( N -- N TRUE )
 toggle_menuitem
 menu-redraw

 \ Now we're going to make the change effective

 dup toggle_stateN @ 0= if
 console_disable
 else
 console_enable
 then

 TRUE \ loop menu again
 ;

 So what has changed? What should i do to make it works again?

 Thanks.




___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Issue with /boot/menu.rc.local after 10.2 update

[Cassiano Peixoto]

Hi guys,

I've been using /boot/menu.rc.local for years to my custom menu option. But
after 10.2 update, it's not working anymore. I always get the message
toggle_menuitem not found on beastie menu.

Here is my /boot/menu.rc.local:

set optionsmenu_init[7]=init_console
set optionsmenu_caption[7]=[C]onsole. Off
set optionstoggled_text[7]=[C]onsole. On
set optionsmenu_command[7]=toggle_console
set optionsmenu_keycode[7]=118
set optionsansi_caption[7]=^[[1mC^[[37monsole. ^[[34;1mOff^[[37m
set optionstoggled_ansi[7]=^[[1mC^[[37monsole. ^[[32;7mOn^[[0;37m

\
\ Console Boot
\

: console_enabled? ( -- flag )
s boot_single getenv -1  dup if
drop ( c-addr flag -- flag )
then
;

: console_enable ( -- )
s set console=comconsole,vidconsole evaluate
;

: console_disable ( -- )
s set console=vidconsole,comconsole evaluate
;

: toggle_console ( N -- N TRUE )
toggle_menuitem
menu-redraw

\ Now we're going to make the change effective

dup toggle_stateN @ 0= if
console_disable
else
console_enable
then

TRUE \ loop menu again
;

So what has changed? What should i do to make it works again?

Thanks.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org