I started "doas ktrace -p " after boot.
However, your clue about "...quotaon(8) could miss the trace file
vnode..." seems relevant here. I did use "doas quotaoff /home" and
"doas quotaon -u /home" while proving to myself how the quota system
works.
The kernel didn't immediately panic after
On Tue, Mar 31, 2020 at 07:01:52AM +, Bryan Stenson wrote:
> yes, but for an unrelated issue (lots of learning in these isolated times).
>
> On Tue, Mar 31, 2020 at 7:00 AM Theo de Raadt wrote:
> >
> > Were you really performing a ktrac of pflogd?
> >
> > Bryan Stenson wrote:
> >
> > >
1. top -SH -s .3 points me that stutters arrive once process changing its state
from 'idle' to 'active' with related disk activity.
2. Any machine with 6.6 GENERIC.MP affected.
2.1. 4-core AMD GX-420CA SOC - stutters more visible;
2.2. 2-core Intel i7-2640m - very rare stutters when
On 31/03/20(Tue) 15:08, Martin wrote:
> 1. top -SH -s .3 points me that stutters arrive once process changing its
> state from 'idle' to 'active' with related disk activity.
What about %spin and %intr?
> 2. Any machine with 6.6 GENERIC.MP affected.
> 2.1. 4-core AMD GX-420CA SOC - stutters
On 3/31/20 3:49 PM, Renaud Allard wrote:
On 3/31/20 11:54 AM, Renaud Allard wrote:
The funny part is that if I relaunch /autoinstall manually after the
failure, it partitions everything as expected.
It seems that when (linux) extended partitions are present, the first
execution of
I just found a CARP BACKUP firewall in the state shown below.
This is the entire console output since restart yesterday.
I'll leave it in this state in case anyone wants additional info.
Until tomorrow morning 6am CEST, that is about 14 hours from now.
Marcus
OpenBSD 6.6 (GENERIC.MP) #7: Thu
On 3/31/20 11:54 AM, Renaud Allard wrote:
The funny part is that if I relaunch /autoinstall manually after the
failure, it partitions everything as expected.
It seems that when (linux) extended partitions are present, the first
execution of "fdisk -iy /dev/rsd0c" doesn't correctly
On 3/31/20 11:38 AM, Renaud Allard wrote:
On 3/31/20 11:25 AM, Stuart Henderson wrote:
On 2020/03/31 11:05, Renaud Allard wrote:
Hello,
I was trying to autoinstall OpenBSD over an existing installation of
linux.
So I used a modified (with upobsd) bsd.rd containing an
auto_install.conf.
On 3/31/20 11:46 AM, Raf Czlonka wrote:
On Tue, Mar 31, 2020 at 10:25:53AM BST, Stuart Henderson wrote:
On 2020/03/31 11:05, Renaud Allard wrote:
Hello,
I was trying to autoinstall OpenBSD over an existing installation of linux.
So I used a modified (with upobsd) bsd.rd containing an
On 3/31/20 11:25 AM, Stuart Henderson wrote:
On 2020/03/31 11:05, Renaud Allard wrote:
Hello,
I was trying to autoinstall OpenBSD over an existing installation of linux.
So I used a modified (with upobsd) bsd.rd containing an auto_install.conf.
But it seems the (MBR) partitioning line is
On Tue, Mar 31, 2020 at 10:25:53AM BST, Stuart Henderson wrote:
> On 2020/03/31 11:05, Renaud Allard wrote:
> > Hello,
> >
> > I was trying to autoinstall OpenBSD over an existing installation of linux.
> > So I used a modified (with upobsd) bsd.rd containing an auto_install.conf.
> > But it
On 2020/03/31 11:05, Renaud Allard wrote:
> Hello,
>
> I was trying to autoinstall OpenBSD over an existing installation of linux.
> So I used a modified (with upobsd) bsd.rd containing an auto_install.conf.
> But it seems the (MBR) partitioning line is never taken into account.
> Using:
> "MBR =
Hello,
I was trying to autoinstall OpenBSD over an existing installation of
linux. So I used a modified (with upobsd) bsd.rd containing an
auto_install.conf.
But it seems the (MBR) partitioning line is never taken into account.
Using:
"MBR = G"
"Use (W)hole disk MBR, whole disk (G)PT or
Ok, makes sense. Honestly, I had forgotten I was running it, but that
IS another wrinkle here.
Thanks for your comments here. I really appreciate the amount of
time/energy this entire project takes. The last thing I want to do is
waste anybody's time. OpenBSD has been rock solid for me, and
On 30/03/20(Mon) 22:11, Stuart Henderson wrote:
> On 2020/03/30 10:29, Martin Pieuchot wrote:
> > On 29/03/20(Sun) 17:17, Stuart Henderson wrote:
> > > [...]
> > > I guess I'll just move it to a wifi network on a different vlan for now.
> >
> > Well I wouldn't be surprise if the issue is exposed
apologies for the double post...please disregard this one.
On Tue, Mar 31, 2020 at 6:51 AM Bryan Stenson wrote:
>
> >Synopsis: panic on vm, ddb prompt on console
> >Category: unknown
> >Environment:
> System : OpenBSD 6.6
> Details : OpenBSD 6.6-current
Bryan Stenson wrote:
> yes, but for an unrelated issue (lots of learning in these isolated times).
>
> On Tue, Mar 31, 2020 at 7:00 AM Theo de Raadt wrote:
> >
> > Were you really performing a ktrac of pflogd?
Well, you should have mentioned that. So we don't have to determine how
you got
yes, but for an unrelated issue (lots of learning in these isolated times).
On Tue, Mar 31, 2020 at 7:00 AM Theo de Raadt wrote:
>
> Were you really performing a ktrac of pflogd?
>
> Bryan Stenson wrote:
>
> > ok...found the panic call here: sys/ufs/ufs/ufs_quota.c:451. From the
> > comment in
Were you really performing a ktrac of pflogd?
Bryan Stenson wrote:
> ok...found the panic call here: sys/ufs/ufs/ufs_quota.c:451. From the
> comment in the code: "On filesystems with quotas enabled, it is an
> error for a file to change size and not to have a dquot structure
> associated with
ooohmaybe related to "softdep"?
https://marc.info/?l=openbsd-misc=139077233507307=2
I don't know the inner workings of ufs and softdep...but maybe this
causes a problem with quotas? Maybe softdep creates a case where a
file can be added/updated without the corresponding dquot structure.
A
ok...found the panic call here: sys/ufs/ufs/ufs_quota.c:451. From the
comment in the code: "On filesystems with quotas enabled, it is an
error for a file to change size and not to have a dquot structure
associated with it."
I do have quotas enabled on /home, but limits are only set for a
single
>Synopsis: panic on vm, ddb prompt on console
>Category: unknown
>Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6-current (GENERIC) #85: Sun Mar 29 10:50:36
MDT 2020
Agreed...I'm not convinced it was due to being hosted on VMM...just
wanted to include that as a data point (perhaps that detail is
stressed too much here).
I'm looking/learning about the "missing dquot" panic message now
(brushing up on CVS, etc). :)
After reboot, the filesystem fsck'd, and all
* Bryan Stenson [2020-03-31 05:57:46 +]:
Synopsis: panic on vm hosted with VMM - missing dquot
Category: unknown
Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6-current (GENERIC) #85: Sun Mar 29
10:50:36 MDT 2020
24 matches
Mail list logo
