On Sat, 06 Mar 2010 14:19:44 +0100
Torfinn Ingolfsen wrote:
> However, the storage pool is not:
> r...@kg-f2# zpool status storage
> pool: storage
> state: UNAVAIL
> status: One or more devices are faulted in response to IO failures.
> action: Make sure the affected devices are connected, then
Dear all:
I'm embarking on some new network stack locking work, which requires me to
address a number of loose ends in the current model. A few years ago, my
attention was drawn to a largly theoretical race, which had existed in the BSD
code since inception. It is detected and handled in pr
On Sun, 7 Mar 2010 11:59:35 + (GMT) Robert Watson wrote:
> Please check the results of the following command:
>
> % sysctl net.inet.tcp.timer_race
> net.inet.tcp.timer_race: 0
Are the results for FreeBSD7 look interesting for you? Because currently we
have mostly FreeBSD7.1 hosts in produ
On Mar 7, 2010, at 12:33 PM, Mikolaj Golub wrote:
> On Sun, 7 Mar 2010 11:59:35 + (GMT) Robert Watson wrote:
>
>> Please check the results of the following command:
>>
>> % sysctl net.inet.tcp.timer_race
>> net.inet.tcp.timer_race: 0
>
> Are the results for FreeBSD7 look interesting for
Hi,
can you try the attached patch please?
This should fix the panic you encountered. Please undo your kernel
changes befoer testing.
Thanks.
Regards,
Alexander Eichner
Mikolaj Golub wrote:
> Hi,
>
> Recently I have updated my 8.0-STABLE i386 system and have learnt that
> virtualbox begins to c
LinkedIn
This is a reminder that on February 26, Igor Lyapin sent you an invitation to
become part of his or her professional network at LinkedIn.
Follow this link to accept Igor Lyapin's invitation.
https://www.linkedin.com/e/doi/1105542438/kg5abXYk/gir_18199627_0/EML-inv_17_
ntpd is a convenient source of multicast packets for testing purposes.
When I add
broadcast 224.0.1.1
to my ntp.conf, ntpd sends a multicast packet with TTL 1 every 64
seconds. Just as expected. However, when I explicitly specify the
TTL as in
broadcast 224.0.1.1 ttl 1
it sends packets with T
Jim Pingle wrote:
On 2/28/2010 10:16 PM, Rui Paulo wrote:
On 1 Mar 2010, at 03:05, Jim Pingle wrote:
On 2/28/2010 9:41 PM, Rui Paulo wrote:
On 1 Mar 2010, at 02:26, Jim Pingle wrote:
Ah, I wasn't aware of wlandebug(8). However, it doesn't seem to operate
on this mwl(4) card. It sets the valu
On 3/7/2010 3:34 PM, Sam Leffler wrote:
> Not following the wlanX naming convention will cause confusion for
> things like rc config files (I believe). Definitely any tool I touched
> expects vap's to be named wlanX.
Duly noted. I wasn't aware of just how many issues would arise from
straying fro
On Sunday 07 March 2010 00:32:21 Jeremy Chadwick wrote:
> On Sat, Mar 06, 2010 at 02:56:07PM -0800, Nick Rogers wrote:
> > ALTQ + RELENG_8 + em(4) will not work at the moment. It does not matter
> > what your PF ruleset looks like or how much traffic you are pushing. The
> > packets that transit th
* Jeremy Chadwick (free...@jdc.parodius.com) wrote:
> It's been mentioned in the past that for "simple" SATA expansion cards,
> a good/affordable choice at this point are cards using the Silicon Image
> 3124/3132/3531 chips (driven by the siis(4) driver). Avoid the 3112.
>
> The reason I say tha
I just did a cvsup and updated my amd64 8.0-STABLE machine, and after
rebooting with the new kernel and all I am seeing the following on directory
access:
default_perms_for_dir: sys_acl_get_file(., ACL_TYPE_DEFAULT): Invalid
argument, falling back on umask
default_perms_for_dir: sys_acl_g
Greetings. I'm testing NanoBSD images for eventual use in an Alix board
and have run into an issue with the boot0cfg lines in the update scripts,
in multiple environments. Specifically, any use of boot0cfg yields a
successful output[1], followed by:
vnode_pager_getpages: I/O read error
At this
13 matches
Mail list logo
