Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error

[Gerrit Kühn]

Am Tue, 28 May 2024 11:25:09 +0200
schrieb Santiago Martinez :

> *"The latest I have is 214.0.286.18"*
> Indeed, the firmware on my box is older, I cannot upgrade it right now, 
> but it is on my to-do list.

Same here, I guess (pkgver). It says
dev.bnxt.0.ver.fw_ver: 214.4.9.10/pkg 214.0.286.18
on both systems.

Also, I don't think I can upgrade the firmware separately, it comes with
the mainboard's bios (which is the latest available).


cu
  Gerrit


smime.p7s
Description: S/MIME cryptographic signature

Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error

[Gerrit Kühn]

Am Tue, 28 May 2024 10:59:00 +0200
schrieb Santiago Martinez :

> Not sure if it will break your setup, but this already happened with 
> 13.2 (I cant recall the exact release).

I have two machines with onboard NICs (Supermicro H12SSL-CT mainboards)
running just fine. One is 13.3, the other is 14.0.

> Drivers used to be ok, before 13.X and then I started to see many errors.

No errors at all on my side here. Do you have onboard NICs or PCIe cards?
From the bugreport linked in earliers mails I can also see that the
firmware I have here appears to be much older than what other people use.
The latest I have is 214.0.286.18.

> is it possible for you to test on that machine and see what happens or 
> its prod?

Well, the 13.3 is production, the 14.0 is configured and loaded with
data, should actually go into production this week (that's why I was
asking... :-). However, I do have a third system of the same hardware that
is unused right now. I could do tests there (given I find some time).


cu
  Gerrit


smime.p7s
Description: S/MIME cryptographic signature

Re: [Bug 269133] bnxt(4): BCM57416 - HWRM_CFA_L2_SET_RX_MASK command returned RESOURCE_ALLOC_ERROR error

[Gerrit Kühn]

Am Mon, 27 May 2024 15:05:31 -0600
schrieb Warner Losh :

> I'd like it there, but I think this will need to be a EN to get it into
> 14.1 given the late date of this commit  Unless we slip 14.1 for
> other reasons...

I have systems running 14.0 that use onboard bnxt  chipsets, seen no issues so far. Does this
mean I'll have to stick with 14.0 as 14.1 will probably break the
interfaces?


cu
  Gerrit


smime.p7s
Description: S/MIME cryptographic signature

Re: noatime on ufs2

[Gerrit Kühn]

Am Sun, 14 Jan 2024 19:14:16 +0100
schrieb "Patrick M. Hausen" :

> That number at first looks like a serious load on the write endurance
> of your SSD. Then, doing the math it turns out it's absolutely
> ridiculous.
> 
> 100 kB/s sums up to 8,640 GB/day (in decimal units). Even the small
> SSDs typically used for embedded devices like firewalls (32 or 64 G
> capacity) have a write endurance in the order of 100 or 200 TBW.
> 
> That's more than 10.000 days or roughly 30 years ...

This highly depends on how your written data are distributed on the disk. I
have seen cases of write amplification by orders of magnitude, e.g., when
adding few bytes on many (several 10k) different files.


cu
  Gerrit


smime.p7s
Description: S/MIME cryptographic signature

Re: why 100 packages are evil

[Gerrit Kühn]

On Sat, 23 Apr 2016 18:52:32 +0100 Matthew Seaman 
wrote about Re: why 100 packages are evil:

MS> > Is freebsd-update going away as result of the new packaging ?

> Yes.  It will be replaced by 'pkg upgrade' -- as far as I know, that's
> the plan for 11.0-RELEASE.

Hm... I never had any troubles with freebsd-update, it always "just
worked" for me. OTOH, I remember having several issues with pkg, requiring
to fix databases manually and so on.


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

Re: Heads up

[Gerrit Kühn]

On Thu, 14 Apr 2016 22:19:23 -0600 Warner Losh  wrote
about Re: Heads up:

WL> Crucial/Micron M500 (all firmware prior to MU07)

I have a couple of these. Where can I get the latest firmware? On
http://www.crucial.com/usa/en/support-ssd they offer only MU05?!


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

Fw: Re: compiling on nfs directories

[Gerrit Kühn]

Hi all,

I have some weird issues compiling software on a Linux client on a nfs
directory served by FreeBSD 10 from a SSD-based RaidZ1. We are not sure
yet what is actually going wrong, but it may be connected to make seeing
wrong timestamps and thus compiling again during the install stage.
I did not have this kind of issue when the NFS-Server was still running
under FreeBSD 8 from a HDD-based RaidZ1.
On freebsd-net, Rick Macklem (see below) suggested to ask here for some
zfs-patches concerning zfs timing attributes that may be an issue here.
Does anybody know something about this?


cu
  Gerrit



Begin forwarded message:

Date: Tue, 16 Dec 2014 08:27:56 -0500 (EST)
From: Rick Macklem rmack...@uoguelph.ca
To: Gerrit Kühn gerrit.ku...@aei.mpg.de
Cc: freebsd-...@freebsd.org
Subject: Re: compiling on nfs directories

[...]

I'm not a ZFS guy, but I thought there was a recent ZFS patch related
to updating a time attribute, but I can't remember if it was atime or
mtime? (You might try a post to freebsd-current@ asking about ZFS time
attributes.)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Future of pf / firewall in FreeBSD ? - does it have one ?

[Gerrit Kühn]

On Fri, 18 Jul 2014 15:06:45 +0400 Gleb Smirnoff gleb...@freebsd.org
wrote about Re: Future of pf / firewall in FreeBSD ? - does it have one ?:

GS The pf mailing list is about a dozen of active people. Yes, they are
GS vocal on the new syntax. But there also exist a large number of common
GS FreeBSD users who simply use pf w/o caring about syntax and reading pf
GS mailing list. If we destroy the syntax compatibility a very large
GS population of users would be hurt, for the sake of making a dozen
GS happy.

I have thought about this for some time now, and I think I do not agree. I
do remember quite well when OpenBSD changed from ipf to pf, and I had to
come up with new rules files. Yes, this is a burden for people maintaining
these systems, but if the thing is well documented and comes with benefits
(like staying in sync with other developers, allowing new features etc.) I
doubt that many people will really be minding this.


cu
  Gerrit
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Request for review/testing: switching the default installer

[Gerrit Kühn]

On Fri, 4 Mar 2011 12:24:20 -0800 Freddie Cash fjwc...@gmail.com wrote
about Re: Request for review/testing: switching the default installer:

FC Or, does anyone have instructions on how to convert the ISO images
FC into memstick images?  Preferably using a Linux station, not a FreeBSD
FC station.

I use unetbootin (http://unetbootin.sourceforge.net/) to create usb
install media from iso images. Works for me.


cu
  Gerrit
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Anybody using gp driver?

[Gerrit Kühn]

On Thu, Nov 27, 2003 at 02:10:22PM -0700, M. Warner Losh wrote:

 I'm wondering if anybody is using, or even able to use, the gpib
 driver.  It uses the old ISA shims, and is one of the drivers that no
 one has acked working in when I ask about the old isa shim drivers.

I always wanted to use it. I have plenty of old ISA GPIB cards here, but
unfortunately I never found the time to play around with them so far.

 I'd also like to say that I'd love to see a good, and proper gpib
 framework in the tree, 

I second this. ;-)

 but it certainly won't be based on this driver!

Oops, is it /that/ bad?

 The questions here are only 'does this driver work?' and 'is anybody
 able to use it?'

Well, as I said above: I'm not using it so far, but given some time I may be
able to find out if it's still working.


cu
  Gerrit
-- 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Anybody using gp driver?

[Gerrit Kühn]

On Fri, Nov 28, 2003 at 01:48:59AM -0700, M. Warner Losh wrote:

 : Oops, is it /that/ bad?

 I can't convince myself that it would have any chance of working.
 That's why I asked.

Hm, doesn't sound very promising then. :)

 : Well, as I said above: I'm not using it so far, but given some time I may be
 : able to find out if it's still working.

 Please let me know if you succeed.

I'll send you a message then. Although I really don't know when I should
find time to play around with those things. I have working gpib PCI/PCMCIA
cards under Linux and need to get some measurements done before I can think
about making things more challanging (like changing over to FreeBSD or 
trying out some of the ancient 8bit cards :-).
Anyway, do I need FreeBSD 4.x for the tests or is there any chance that 5.x
will work with this driver, too?

BTW: Are there more people around (except for you and me :-) who would like 
to see decent gpib-support in FreeBSD? I can remember that even the free 
gpib driver for Linux was unmaintained for some years until it became almost
unusable (only for kernel 2.0.x then, with 2.4.x already out in the streets).
Luckily some people have taken up the development some months ago, so there
is a version working for 2.4.x now.
Is there any chance to benefit from the Linux driver, or will a FreeBSD
driver require to be rewritten from scratch?


cu
  Gerrit
-- 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Anybody using gp driver?

[Gerrit Kühn]

On Fri, Nov 28, 2003 at 05:03:22PM +0100, Poul-Henning Kamp wrote:

 BTW: Are there more people around (except for you and me :-) who would like 
 to see decent gpib-support in FreeBSD?

 Yes, me.

I might have guessed it. 
Is there anything around FreeBSD you're not working with or on? ;-)

 I'm currently running on a hacked up GPIB from userland I did myself,
 unfortunately it works well enough that I have never gotten around to
 push it into the kernel.
 
   http://phk.freebsd.dk/patch/GPIB.tgz

Perhaps I'll be able to have a look at it next week. Which gpib chipsets
does it support (apart from NI, which seems to be some kind of standard)?

 On the other hand, GPIB is not going to be a major market for us, but 
 merely a fringe convenience feature I suspect.

Hm, FreeBSD is not supposed to do measurements and steering devices? When I
was looking for an OS with gpib support apart from Windows some time ago, 
the only thing I could find was an old driver for Linux 2.0.x and the one
for FreeBSD; even NetBSD didn't offer gpib support, though I supposed that 
it is more targeted to that kind of things.
Now we have most of our high-level software for gpib written in Java, and 
it runs on Linux and Windows. For BSD I would just need the driver (and
probably a new JNI).


cu
  Gerrit
-- 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Anybody using gp driver?

[Gerrit Kühn]

On Fri, Nov 28, 2003 at 09:17:54AM -0800, Frank Mayhar wrote:

   http://people.freebsd.org/~tg/gpib.Sep22b.tar.gz
 
 (Galbraith's old site is dead.)
 
 Just FYI, so that others can avoid the inconvenience of doing the same
 search.

Thanks!


cu
  Gerrit
-- 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: VIA C3

[Gerrit Kühn]

On Wed, Jun 18, 2003 at 10:44:17AM -0400, Damian Gerow wrote:

 I have an Ezra or an Ezra-T core (the only difference is Tualatin sp
 compatibility), and it produces an Unknown.

 If you have a 'Samuel2' core, then you have a Samuel2 core.  It's neither
 Ezra nor Ezra-T -- those two are the successors to Samuel2.

Well, all I can say is, that I bought it as Ezra and there is Ezra
printed on it. FreeBSD identifies it as Samuel2, though.

  However, if you have a C3 without SSE, it's basically a K6 with MMX
  and 3dNow. So I'm using CPUTYPE=k6-3 in /etc/make.conf. Up to now
  this has been working fine for me.

 I've been using CPUTYPE=i586/mmx.  That's been working for me as well -- I'd
 be interested to see which is more optimized.

I don't know. But I think there are only rare cases where you will
notice differences.

 Does your chip understand CMOV?  GCC presumes that a 686-class processor has
 CMOV, and while the C3 /is/ a 686-class processor, it doesn't do CMOV.  But
 I heard a rumor that the Samuel2 core /does/ do CMOV...

I guess it doesn't understand CMOV. I can remember trying i686 first
and having problems with several applications then... afair
/usr/ports/editors/joe was among them (crashed when starting). I had
already heard about that CMOV thing then and blamed the crashes on the
i686-setting. Since I moved to k6-3, everything is just fine.


cu
  Gerrit
-- 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: VIA C3

[Gerrit Kühn]

On Wed, Jun 18, 2003 at 11:10:49AM -0400, Damian Gerow wrote:

  Well, all I can say is, that I bought it as Ezra and there is Ezra
  printed on it. FreeBSD identifies it as Samuel2, though.

 And I bought my Ezra as a Nehemiah.

[...]

 So maybe they do have a way to distinguish the chips.  Dunno -- at the very
 least, it's not marketed.  And the Samuel2 is definitely not an Ezra.

Thanks for the clarification. I'm almost sure that there was something
with ezra printed right on the cpu, but I can't remember for sure;
so maybe you're right with the assumption that it's in fact a Samuel2.

 FWIW, the best way I've seen to figure out which chip you're using (at least
 between Ezra/Ezra-T and Nehemiah) is to look at the clocking -- Ezra/Ezra-T
 seems to be 100*10.0, whereas Nehemiah seems to be 133*7.5.

Back to the performance-discussion between cputype 586/mmx and k6-3
optimization: do you have a suggestion how to benchmark it?


cu
  Gerrit
-- 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: VIA C3

[Gerrit Kühn]

On Fri, Jun 13, 2003 at 06:33:56PM -0700, David Yeske wrote:

 Anyone have a VIA C3?  I'm running FreeBSD current
 on one and I don't see any gcc flags for the VIA C3.
 I think it has MMX and 3dnow, but it does not have SSE?

Up to the Ezra kernel the C3 doesn't suppoert SSE. Only the newest
C3-kernel named Nehemiah does have it.

 I was wondering what gcc flags other VIA C3 users
 are using on FreeBSD.  I am not sure what 
 optimizations are safe for this cpu running FreeBSD.

 CPU: VIA/IDT Unknown (998.70-MHz 686-class CPU)
   Origin = CentaurHauls  Id = 0x689  Stepping = 9
   Features=0x803035FPU,DE,TSC,MSR,MTRR,PGE,MMX

This one doesn't seem to support SSE, though I wonder why there is
this unknown. My C3 here is an Ezra and is identified as Samuel2
with id=067a.

However, if you have a C3 without SSE, it's basically a K6 with MMX
and 3dNow. So I'm using CPUTYPE=k6-3 in /etc/make.conf. Up to now
this has been working fine for me.



cu
  Gerrit
-- 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Does bg fsck have problems with large filesystems?

[Gerrit Kühn]

On Tue, Jan 28, 2003 at 06:31:42PM +0100, Gerrit Kühn wrote:

  I've been trying to reproduce this bug on my desktop. This machine has 2
  80gb disks, one of which is dedicated with one slice. So far, after 8 hard
  resets, I haven't had any problem with either the machine or bgfsck
  hanging. 

 I'll try to reproduce the thing on my machine as soon as possible.
 Perhaps it was just because it was Monday, who knows...

Meanwhile I found out that my problem is 100% reproducible.

My file systems look like this:

Filesystem  1K-blocksUsedAvail Capacity  Mounted on
/dev/ad0s1a257838   67338   16987428%/
devfs   1   10   100%/dev
/dev/ad0s1g  57467672   2 52870258 0%/export
/dev/ad0s1f   4125838   4  3795768 0%/tmp
/dev/ad0s1e  12383502 1336152 1005667012%/usr
/dev/ad0s1d   41258383458  3792314 0%/var


When booting with non-clean filesystems, bgfsck runs quickly over a,
d, e and f. However, on g it keeps running forever. I can't kill the
fsck processes and I can't access g, though the rest of the system
seems to be usable as usual. Here is the output of ps axl:

  UID   PID  PPID CPU PRI NI   VSZ  RSS MWCHAN STAT  TT   TIME COMMAND
0 0 0   0 -16  0 0   12 sched  DLs   ??0:00.00  (swapper)
0 1 0   0   8  0   712  392 wait   ILs   ??0:00.01 /sbin/init -
0 2 0   0  -8  0 0   12 g_even DL??0:00.02  (g_event)
0 3 0   0  -8  0 0   12 g_up   DL??0:00.09  (g_up)
0 4 0   0  -8  0 0   12 g_down DL??0:00.19  (g_down)
0 5 0   0 -84  0 0   12 actask IL??0:00.00  (acpi_task0
0 6 0   0 -84  0 0   12 actask IL??0:00.00  (acpi_task1
0 7 0   0 -84  0 0   12 actask IL??0:00.00  (acpi_task2
0 8 0   0 -16  0 0   12 psleep DL??0:00.00  (pagedaemon
0 9 0   0  20  0 0   12 psleep DL??0:00.00  (vmdaemon)
010 0   0 -16  0 0   12 ktrace DL??0:00.00  (ktrace)
011 0 110 -16  0 0   12 -  RL??2:20.07  (idle)
012 0   0 -48  0 0   12 -  WL??0:00.12  (swi6: tty:
014 0   0 -44  0 0   12 -  WL??0:00.00  (swi1: net)
015 0   0  76  0 0   12 sleep  DL??0:00.05  (random)
019 0   0 -28  0 0   12 -  WL??0:00.00  (swi5: acpi
022 0   0 -64  0 0   12 -  WL??0:00.28  (irq14: ata
024 0   0 -68  0 0   12 -  WL??0:00.00  (irq11: rl0
025 0   0   8  0 0   12 usbevt DL??0:00.00  (usb0)
026 0   0   8  0 0   12 usbtsk DL??0:00.00  (usbtask)
027 0   0   8  0 0   12 usbevt DL??0:00.00  (usb1)
028 0   5 -68  0 0   12 -  WL??0:00.00  (irq12: fwo
029 0   0 -64  0 0   12 -  WL??0:00.00  (irq6: fdc0
032 0   0 -60  0 0   12 -  WL??0:00.00  (irq7: ppc0
033 0   0 -60  0 0   12 -  WL??0:00.02  (irq1: atkb
036 0  34 171  0 0   12 pgzero DL??0:00.47  (pagezero)
037 0   2  -4  0 0   12 snaplk DL??0:00.24  (bufdaemon)
038 0   0  20  0 0   12 syncer DL??0:00.01  (syncer)
039 0   0  -4  0 0   12 vlruwt DL??0:00.00  (vnlru)
040 0   0   8  0 0   12 nfsidl IL??0:00.00  (nfsiod 0)
041 0   0   8  0 0   12 nfsidl IL??0:00.00  (nfsiod 1)
042 0   0   8  0 0   12 nfsidl IL??0:00.00  (nfsiod 2)
043 0   0   8  0 0   12 nfsidl IL??0:00.00  (nfsiod 3)
0   246 1   0  96  0  1172  736 select Ss??0:00.03 /usr/sbin/sy
0   267 1   0  96  0  1372 1016 select Ss??0:00.03 /usr/sbin/rp
0   350 1 155 115  0  1220  992 select Is??0:00.01 /usr/sbin/mo
0   353 1 112 110  0  1168  876 select Is??0:00.13 nfsd: master
0   355   353 155   4  0  1128  748 nfsd   I ??0:00.00 nfsd: server
0   356   353 155   4  0  1128  748 nfsd   I ??0:00.00 nfsd: server
0   357   353 155   4  0  1128  748 nfsd   I ??0:00.00 nfsd: server
0   358   353 155   4  0  1128  748 nfsd   I ??0:00.00 nfsd: server
0   374 1   0  96  0  1144  680 select Ss??0:00.00 /usr/sbin/us
0   394 1 154 115  0  1196  808 select Is??0:00.01 /usr/sbin/lp
0   454 1 153 115  0  3092 2200 select Is??0:00.63 /usr/sbin/ss
0   460 1   0  96  0  3092 2544 select Ss??0:00.01 sendmail: ac
   25   463 1 153  20  0  2992 2500 pause  Is??0:00.00 sendmail: Qu
0   512 1   0   8  0  1236  956 nanslp Ss??0:00.01 /usr/sbin/cr
0   522 1   0   8  0  1532 1236

Re: Does bg fsck have problems with large filesystems?

[Gerrit Kühn]

On Tue, Jan 28, 2003 at 11:44:03AM +0100, Attila Nagy wrote:

  I've just installed my first 5.0-rel system and did some
  torture-testing. When resetting the machine to test the backgrounded
  fsck I experienced the following problem: All filesystems came back
  quickly and bg fsck worked fine, except for one. I had created a large
  (50GB) /export filesystem on with fsck reproducively hang.

 See PR kern/47105.
 Although it speaks of much larger filesystems, than your, the problem is
 there.

47105 seems to be slightly different from what I saw, because my
machine never paniced; the fsck just hung forever.

 I've already written to Kirk McKusick, but it seems that he has a lot of
 work, because I didn't get answer.

Ok, then things are already on their way, I guess.

 If anybody wants to look into this problem, I can give access to the
 machine (even serial console)...

I wonder if it's only the large filesystem that triggers this problem.
Actually I think that my 50GB are not /that/ large, and someone else
should have noticed the problem before.
BTW: As mentioned in the PR one workaround is to turn off bg fsck. On
the other hand bg fsck is working fine on smaller filesystems. Is
there a way to turn bg fsck off for just one partition?


cu
  Gerrit
-- 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Does bg fsck have problems with large filesystems?

[Gerrit Kühn]

On Tue, Jan 28, 2003 at 12:22:10PM -0500, Andre Guibert de Bruet wrote:


 I've been trying to reproduce this bug on my desktop. This machine has 2
 80gb disks, one of which is dedicated with one slice. So far, after 8 hard
 resets, I haven't had any problem with either the machine or bgfsck
 hanging. 

I'll try to reproduce the thing on my machine as soon as possible.
Perhaps it was just because it was Monday, who knows...


cu
  Gerrit
-- 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Does bg fsck have problems with large filesystems?

[Gerrit Kühn]

On Tue, Jan 28, 2003 at 04:23:08PM +0100, Attila Nagy wrote:

  47105 seems to be slightly different from what I saw, because my machine
  never paniced; the fsck just hung forever.

 It depends. My machine hangs, there's no panic.

Yes, I overlooked that in the PR when I read it first. Mine was still
usable: I could switch VTs and even log in, but I couldn't do anything
about the hanging fsck processes.

   I've already written to Kirk McKusick, but it seems that he has a lot
   of work, because I didn't get answer.
  Ok, then things are already on their way, I guess.
 Don't know, but I hope :)

That makes two of us. :)

  I wonder if it's only the large filesystem that triggers this problem.
  Actually I think that my 50GB are not /that/ large, and someone else
  should have noticed the problem before.
 I wonder what's the common in our case, then.

I really don't know. I have a SV25 barebone system from Shuttle (VIA
Twister Chipset) and an IBM deskstar 80GB IDE HD. Does that sound
familiar to you?

  BTW: As mentioned in the PR one workaround is to turn off bg fsck. On
  the other hand bg fsck is working fine on smaller filesystems. Is there
  a way to turn bg fsck off for just one partition?

 I don't know any. BTW, the big partitions are those which needs the extra
 time, so it is very likely that you won't benefit too much from this...

Well, the drive has 80GB, the big partition is 50GB, so I would save
something like 3/8 of the time. Not too much, but better than nothing,
I thought. ;)


cu
  Gerrit
-- 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Does bg fsck have problems with large filesystems?

[Gerrit Kühn]

On Tue, Jan 28, 2003 at 12:34:25PM -0500, Robert Watson wrote:


 Following reports of problems with bgfsck during the 5.0-RC series, and
 prior to the release, I spent some time adding hard disks to machines,
 resetting without clean shutdowns, and then interrupting background fscks,
 piles of builds going, etc. When I started, it was fairly problematic, but
 after Kirk's last batch of buffer fixes, etc, it was pretty much 100%
 reliable on the boxes I was testing on.  

Have these fixes been applied to 5.0-rel, too? If not, I'm considering
updating to -current.


cu
  Gerrit
-- 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Does bg fsck have problems with large filesystems?

[Gerrit Kühn]

Hi all,

I've just installed my first 5.0-rel system and did some
torture-testing. When resetting the machine to test the backgrounded
fsck I experienced the following problem:
All filesystems came back quickly and bg fsck worked fine, except for
one. I had created a large (50GB) /export filesystem on with fsck
reproducively hang. I also couldn't reboot the system cleanly anymore,
because of those fsck processes not going away.
Finally, I commented out /export from /etc/fstab and run fsck manually
in fg mode after the rest of the system had been checked cleanly.
There were a few errors, and after that the check finished and marked
the system as clean. However, mounting the clean system took several
seconds and gave me this message from the kernel:
FFS_SNAPSHOT_MOUNT: old format snapshot inode 4
Well, whatever... :)

Nevertheless everything is working fine now, again. I havn't checked
yet, but will this happen every time my systems reboots without
unmounting the filesystems cleanly? Is anything wrong with filesystems
that large, or could I have done anything else that causes this strange
behaviour?


cu
  Gerrit
-- 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: USB and Kodak DC4800 Camera

[Gerrit Kühn]

On Thu, Jan 02, 2003 at 02:11:16PM +0100, Michael Class wrote:

 I am facing a problem that my Kodak DC4800 Camera is not recognized by a 
 current FreeBSD-current system (I do not have release systems around, so 
 I can not test aginst them, but I suspect that it would not work their 
 either) (and yes, it works on the same system with L***x and W*e :-(

I have similar problems with USB-ports under -current (still dp2 here)
with *any* kind of USB device (tried printer, scanner...). Can you
tell if other USB devices do work for you?


cu
  Gerrit
-- 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Current hangs in reboot

[Gerrit Kühn]

On Wed, Dec 11, 2002 at 03:35:52PM +0200, Taavi Talvik wrote:

  Waiting (max 60 seconds) for system process `vnlru' to stop...stopped

 Turning off ACPI makes it reboot. Thanks for suggestion Gerrit!

You're welcome. I just noticed I forgot to include the mailinglist in
my answers to you. :)

 But how is ACPI related to problem? Why rebooting hangs between
 stoping `vnlru' and `bufdaemon' in ACPI case?

I'd like to know that, too. :-)


cu
  Gerrit
-- 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message