Re: network probs rxcsum
On 05/19/10 12:44, Jeremy Chadwick wrote: > On Wed, May 19, 2010 at 12:34:17PM +0200, Mark Stapper wrote: > >> I have two machines running FreeBSD amd64 8.0-Stable with custom kernels. >> My newer box has had troubles with ssh from day one. >> I hoped a kernel upgrade would help, but it didn't. >> When I'd ssh into the box ssh would exit with errors: >> Bad packet length xx >> Disconnecting: Packet corrupt. >> >> after issueing: "ifconfig em0 -rxcons" everything was stable again. >> First I figured it'd be a driver issue. However, I use the same NIC in >> my other box! >> What could be causing this problem? >> > I think you mean "-rxcsum", not "-rxcons". > > Could you please provide output from the following commands? Jack Vogel > will probably respond later about this, but said output would help him. > > - uname -a > - dmesg | grep em0 > - pciconf -lvc > > Thanks. > > Could it be a shared interrupt problem? Even though ssh worked with rxcsup disabled, network performance was horrible! Using my onboard nick in stead of em0 cleared it right up! em0 is a pci addon card. Here are the outputs you requested: [r...@mario ~]# uname -a FreeBSD mario 8.0-STABLE FreeBSD 8.0-STABLE #0: Tue May 18 19:37:30 CEST 2010 root@:/usr/obj/usr/src/sys/mario amd64 [r...@mario ~]# dmesg |grep em0 em0: port 0x9c00-0x9c3f mem 0xfdfa-0xfdfb,0xfdfc-0xfdfd irq 18 at device 6.0 on pci2 em0: [FILTER] em0: Ethernet address: 00:1b:21:4b:8b:85 em0: link state changed to UP em0: link state changed to DOWN em0: link state changed to UP em0: link state changed to DOWN em0: link state changed to UP em0: link state changed to DOWN em0: link state changed to UP em0: link state changed to DOWN em0: link state changed to UP em0: link state changed to DOWN [r...@mario ~]# pciconf -lvc no...@pci0:0:0:0: class=0x05 card=0x02f010de chip=0x02f410de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'C51 Host Bridge' class = memory subclass = RAM cap 08[44] = HT slave cap 08[e0] = HT MSI address window disabled at 0xfee0 no...@pci0:0:0:1: class=0x05 card=0x02fa10de chip=0x02fa10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'C51 Memory Controller 0' class = memory subclass = RAM no...@pci0:0:0:2: class=0x05 card=0x02fe10de chip=0x02fe10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'C51 Memory Controller 1' class = memory subclass = RAM no...@pci0:0:0:3: class=0x05 card=0x02f810de chip=0x02f810de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'C51 Memory Controller 5' class = memory subclass = RAM no...@pci0:0:0:4: class=0x05 card=0x02f910de chip=0x02f910de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'C51 Memory Controller 4' class = memory subclass = RAM no...@pci0:0:0:5: class=0x05 card=0x02ff10de chip=0x02ff10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'C51 Host Bridge' class = memory subclass = RAM cap 00[44] = unknown no...@pci0:0:0:6: class=0x05 card=0x027f10de chip=0x027f10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'C51 Memory Controller 3' class = memory subclass = RAM no...@pci0:0:0:7: class=0x05 card=0x027e10de chip=0x027e10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'C51 Memory Controller 2' class = memory subclass = RAM pc...@pci0:0:4:0: class=0x060400 card=0x10de chip=0x02fb10de rev=0xa1 hdr=0x01 vendor = 'NVIDIA Corporation' device = 'C51 PCIe Bridge' class = bridge subclass = PCI-PCI cap 0d[40] = PCI Bridge card=0x10de cap 01[48] = powerspec 2 supports D0 D3 current D0 cap 05[50] = MSI supports 2 messages, 64 bit cap 08[60] = HT MSI address window disabled at 0xfee0 cap 10[80] = PCI-Express 1 root port max data 128(128) link x16(x16) no...@pci0:0:8:0: class=0x05 card=0xcb8410de chip=0x036910de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'MCP55 Memory Controller' class = memory subclass = RAM cap 08[44] = HT slave cap 08[dc] = HT MSI address window enabled at 0xfee0 is...@pci0:0:9:0: class=0x060100 card=0xcb8410de chip=0x036010de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'MCP55 LPC Bridge' class = bridge
Re: Buzzing snd_emu10kx enabled card with r206173
On 18/05/2010 08:14, Mark Stapper wrote: > On 18/05/2010 00:22, Garrett Cooper wrote: > >> On Mon, May 17, 2010 at 11:21 AM, Mark Stapper wrote: >> >> >>> On 12/04/2010 16:29, Garrett Cooper wrote: >>> >>> >>>> On Tue, Apr 6, 2010 at 3:39 AM, Garrett Cooper wrote: >>>> >>>> >>>> >>>>> On Mon, Apr 5, 2010 at 12:26 PM, Garrett Cooper >>>>> wrote: >>>>> >>>>> >>>>> >>>>>> On Mon, Apr 5, 2010 at 11:22 AM, Garrett Cooper >>>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>>> Hi, >>>>>>>When I first installed FreeBSD on this machine, I had a heck of a >>>>>>> time getting the soundcard's PCM channel to function properly. It >>>>>>> would buzz incessantly when I played any audio on it; I disabled the >>>>>>> onboard snd_hda enabled audio and things magically worked, until >>>>>>> today. After a kernel upgrade and a few warm boots, I'm back to where >>>>>>> I started from -- the PCM channel buzzes whenever I play audio; >>>>>>> line-in works perfectly fine however. I'm not seeing anything out of >>>>>>> the ordinary in commits over the past couple of weeks for the pcm >>>>>>> pieces (the last successful kernel I used was 2~3 weeks old). >>>>>>>Are there any device_printf's I should add or a debug procedure >>>>>>> that you recommend I do to triage the situation? >>>>>>> Thanks, >>>>>>> -Garrett >>>>>>> >>>>>>> # uname -a >>>>>>> FreeBSD bayonetta.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r206173M: >>>>>>> Sun Apr 4 19:54:22 PDT 2010 >>>>>>> r...@bayonetta.local:/usr/obj/usr/src/sys/BAYONETTA amd64 >>>>>>> # pciconf -lv | grep -A 4 emu >>>>>>> emu10...@pci0:8:0:0:class=0x040100 card=0x10211102 chip=0x00081102 >>>>>>> rev=0x00 hdr=0x00 >>>>>>>vendor = 'Creative Technology LTD.' >>>>>>>device = 'sound blaster Audigy 2 (ca0108)' >>>>>>>class = multimedia >>>>>>>subclass = audio >>>>>>> # dmesg | grep 'irq 16' >>>>>>> uhci0: port 0xa800-0xa81f >>>>>>> irq 16 at device 26.0 on pci0 >>>>>>> pcib7: irq 16 at device 28.1 on pci0 >>>>>>> emu10kx0: port 0xec00-0xec3f irq 16 at >>>>>>> device 0.0 on pci8 >>>>>>> # dmesg | grep 'pcm' >>>>>>> pcm0: on emu10kx0 >>>>>>> pcm0: >>>>>>> pcm1: on emu10kx0 >>>>>>> pcm2: on emu10kx0 >>>>>>> pcm3: on emu10kx0 >>>>>>> pcm4: on emu10kx0 >>>>>>> >>>>>>> >>>>>>> >>>>>> Some more information: >>>>>> >>>>>> 1. snd_emu10kx and sound are both modules loaded on boot, along with >>>>>> if_re, linux, and nvidia. >>>>>> 2. Disabling nvidia -> no change. >>>>>> 3. Disabling acpi -> unbootable system because many drivers can't map >>>>>> interrupts without it (can't test unless I isolate the drivers and >>>>>> enable them one by one -- something I'll try later on). >>>>>> >>>>>> I'm at a loss right now... my hunch is that it's potentially a bad >>>>>> interaction between the snd_emu10kx driver and another driver on the >>>>>> same PCI bus (which is just the ACPI and uhci drivers), but I can't >>>>>> test these claims. There are other funky things about my system that >>>>>> have changed over the past couple of kernel versions, like front USB >>>>>> ports could charge my iPhone, and now they don't... and the fact that >>>>>> ACPI blanking via nvidia now works again... so something may have >>>>>> changed on the backend, but I'm not 100% sure on what I should isolate >>>>>> as the root cause,
Re: Buzzing snd_emu10kx enabled card with r206173
On 25/05/2010 20:05, Garrett Cooper wrote: > On Tue, May 25, 2010 at 3:06 AM, Mark Stapper wrote: > >> On 18/05/2010 08:14, Mark Stapper wrote: >> >>> On 18/05/2010 00:22, Garrett Cooper wrote: >>> >>> >>>> On Mon, May 17, 2010 at 11:21 AM, Mark Stapper wrote: >>>> >>>> >>>> >>>>> On 12/04/2010 16:29, Garrett Cooper wrote: >>>>> >>>>> >>>>> >>>>>> On Tue, Apr 6, 2010 at 3:39 AM, Garrett Cooper >>>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> On Mon, Apr 5, 2010 at 12:26 PM, Garrett Cooper >>>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Mon, Apr 5, 2010 at 11:22 AM, Garrett Cooper >>>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Hi, >>>>>>>>>When I first installed FreeBSD on this machine, I had a heck of a >>>>>>>>> time getting the soundcard's PCM channel to function properly. It >>>>>>>>> would buzz incessantly when I played any audio on it; I disabled the >>>>>>>>> onboard snd_hda enabled audio and things magically worked, until >>>>>>>>> today. After a kernel upgrade and a few warm boots, I'm back to where >>>>>>>>> I started from -- the PCM channel buzzes whenever I play audio; >>>>>>>>> line-in works perfectly fine however. I'm not seeing anything out of >>>>>>>>> the ordinary in commits over the past couple of weeks for the pcm >>>>>>>>> pieces (the last successful kernel I used was 2~3 weeks old). >>>>>>>>>Are there any device_printf's I should add or a debug procedure >>>>>>>>> that you recommend I do to triage the situation? >>>>>>>>> Thanks, >>>>>>>>> -Garrett >>>>>>>>> >>>>>>>>> # uname -a >>>>>>>>> FreeBSD bayonetta.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r206173M: >>>>>>>>> Sun Apr 4 19:54:22 PDT 2010 >>>>>>>>> r...@bayonetta.local:/usr/obj/usr/src/sys/BAYONETTA amd64 >>>>>>>>> # pciconf -lv | grep -A 4 emu >>>>>>>>> emu10...@pci0:8:0:0:class=0x040100 card=0x10211102 chip=0x00081102 >>>>>>>>> rev=0x00 hdr=0x00 >>>>>>>>>vendor = 'Creative Technology LTD.' >>>>>>>>>device = 'sound blaster Audigy 2 (ca0108)' >>>>>>>>>class = multimedia >>>>>>>>>subclass = audio >>>>>>>>> # dmesg | grep 'irq 16' >>>>>>>>> uhci0: port 0xa800-0xa81f >>>>>>>>> irq 16 at device 26.0 on pci0 >>>>>>>>> pcib7: irq 16 at device 28.1 on pci0 >>>>>>>>> emu10kx0: port 0xec00-0xec3f irq 16 at >>>>>>>>> device 0.0 on pci8 >>>>>>>>> # dmesg | grep 'pcm' >>>>>>>>> pcm0: on emu10kx0 >>>>>>>>> pcm0: >>>>>>>>> pcm1: on emu10kx0 >>>>>>>>> pcm2: on emu10kx0 >>>>>>>>> pcm3: on emu10kx0 >>>>>>>>> pcm4: on emu10kx0 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> Some more information: >>>>>>>> >>>>>>>> 1. snd_emu10kx and sound are both modules loaded on boot, along with >>>>>>>> if_re, linux, and nvidia. >>>>>>>> 2. Disabling nvidia -> no change. >>>>>>>> 3. Disabling acpi -> unbootable system because many drivers can't map >>>>>>>> interrupts without it (can't test unless I isolate the drivers and >>>>>>>> enable them one by o
Re: Buzzing snd_emu10kx enabled card with r206173
On 25/05/2010 20:05, Garrett Cooper wrote: > On Tue, May 25, 2010 at 3:06 AM, Mark Stapper wrote: > >> On 18/05/2010 08:14, Mark Stapper wrote: >> >>> On 18/05/2010 00:22, Garrett Cooper wrote: >>> >>> >>>> On Mon, May 17, 2010 at 11:21 AM, Mark Stapper wrote: >>>> >>>> >>>> >>>>> On 12/04/2010 16:29, Garrett Cooper wrote: >>>>> >>>>> >>>>> >>>>>> On Tue, Apr 6, 2010 at 3:39 AM, Garrett Cooper >>>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> On Mon, Apr 5, 2010 at 12:26 PM, Garrett Cooper >>>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> On Mon, Apr 5, 2010 at 11:22 AM, Garrett Cooper >>>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> Hi, >>>>>>>>>When I first installed FreeBSD on this machine, I had a heck of a >>>>>>>>> time getting the soundcard's PCM channel to function properly. It >>>>>>>>> would buzz incessantly when I played any audio on it; I disabled the >>>>>>>>> onboard snd_hda enabled audio and things magically worked, until >>>>>>>>> today. After a kernel upgrade and a few warm boots, I'm back to where >>>>>>>>> I started from -- the PCM channel buzzes whenever I play audio; >>>>>>>>> line-in works perfectly fine however. I'm not seeing anything out of >>>>>>>>> the ordinary in commits over the past couple of weeks for the pcm >>>>>>>>> pieces (the last successful kernel I used was 2~3 weeks old). >>>>>>>>>Are there any device_printf's I should add or a debug procedure >>>>>>>>> that you recommend I do to triage the situation? >>>>>>>>> Thanks, >>>>>>>>> -Garrett >>>>>>>>> >>>>>>>>> # uname -a >>>>>>>>> FreeBSD bayonetta.local 9.0-CURRENT FreeBSD 9.0-CURRENT #1 r206173M: >>>>>>>>> Sun Apr 4 19:54:22 PDT 2010 >>>>>>>>> r...@bayonetta.local:/usr/obj/usr/src/sys/BAYONETTA amd64 >>>>>>>>> # pciconf -lv | grep -A 4 emu >>>>>>>>> emu10...@pci0:8:0:0:class=0x040100 card=0x10211102 chip=0x00081102 >>>>>>>>> rev=0x00 hdr=0x00 >>>>>>>>>vendor = 'Creative Technology LTD.' >>>>>>>>>device = 'sound blaster Audigy 2 (ca0108)' >>>>>>>>>class = multimedia >>>>>>>>>subclass = audio >>>>>>>>> # dmesg | grep 'irq 16' >>>>>>>>> uhci0: port 0xa800-0xa81f >>>>>>>>> irq 16 at device 26.0 on pci0 >>>>>>>>> pcib7: irq 16 at device 28.1 on pci0 >>>>>>>>> emu10kx0: port 0xec00-0xec3f irq 16 at >>>>>>>>> device 0.0 on pci8 >>>>>>>>> # dmesg | grep 'pcm' >>>>>>>>> pcm0: on emu10kx0 >>>>>>>>> pcm0: >>>>>>>>> pcm1: on emu10kx0 >>>>>>>>> pcm2: on emu10kx0 >>>>>>>>> pcm3: on emu10kx0 >>>>>>>>> pcm4: on emu10kx0 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> Some more information: >>>>>>>> >>>>>>>> 1. snd_emu10kx and sound are both modules loaded on boot, along with >>>>>>>> if_re, linux, and nvidia. >>>>>>>> 2. Disabling nvidia -> no change. >>>>>>>> 3. Disabling acpi -> unbootable system because many drivers can't map >>>>>>>> interrupts without it (can't test unless I isolate the drivers and >>>>>>>> enable them one by o
Re: Buzzing snd_emu10kx enabled card with r206173
On 30/05/2010 08:31, Garrett Cooper wrote: > On Wed, May 26, 2010 at 12:05 PM, Mark Stapper wrote: > >> On 25/05/2010 20:05, Garrett Cooper wrote: >> >>> On Tue, May 25, 2010 at 3:06 AM, Mark Stapper wrote: >>> >>> >>>> On 18/05/2010 08:14, Mark Stapper wrote: >>>> >>>> >>>>> On 18/05/2010 00:22, Garrett Cooper wrote: >>>>> >>>>> >>>>> >>>>>> On Mon, May 17, 2010 at 11:21 AM, Mark Stapper wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> I have the same problem. >>>>>>> I'll try compiling the driver in the kernel. >>>>>>> >>>>>>> >>>>>> FWIW I've compiled the driver into the kernel for several >>>>>> iterations now and it works like a champ, so there's something with >>>>>> the sound subsystem that isn't jiving properly when loading from >>>>>> modules... >>>>>> HTH, >>>>>> -Garrett >>>>>> >>>>>> >>>>>> >>>>>> >>>>> Thanks for the info. >>>>> I've noticed that when I load the kernel module at startup (by adding it >>>>> to loader.conf) chances of it working improve. >>>>> If I load it afterwards, the nice huff puff sounds come out of my >>>>> speaker again. >>>>> Compiling the new and improved kernel today. >>>>> Thanks for your help. >>>>> >>>> I compiled the emu10kx driver into the kernel. >>>> That seemed to work, but now the hissing and buzzing is back. >>>> I really don't know what is going on anymore.. >>>> Any thoughts? >>>> >>>> >>> What modules have you compiled and loaded? >>> >> Kernel config and kldstat output pasted below >> >> > [...] > > >> > Everything I saw there appeared sane (it would have been nice to grab > the -v output from kldstat, but that's ok...). Let's try doing the > following: > > 1. Add `options EMU_MTX_DEBUG' to your kernconf. > 2. Add set the sysctl: dev.emu10kx.0.debug=1 . > > Let's see if anything changes... > > Also, if you could provide some more hardware stats (say dmesg.boot > and/or devinfo -v) and version stats (I already know that you're > running amd64 from your kernel config) for the OS that would be > helpful as well. > > I'm going to try upgrading my kernel and I'll try these steps as well. > The locking between this driver and some other sound drivers isn't > exactly the same (interestingly enough this driver uses Giant locking > for some bits, while the ich one doesn't), and there were some past > bugs with other branches of *BSD's drivers related to pci bus > commands, etc; the other BSDs have dramatically different soundsystems > -- I assume the old school soundsystem, s.t. the issues are probably > not the same. > > Thanks, > -Garrett > I'm building the new kernel as we e-mail. The option "EMU_MTX_DEBUG doesn't seem to excist thought. Used SND_DEBUG instead. here are the requested outputs: nexus0 apic0 ram0 acpi0 cpu0 pnpinfo _HID=none _UID=0 at handle=\_PR_.C000 acpi_perf0 powernow0 cpufreq0 cpu1 pnpinfo _HID=none _UID=0 at handle=\_PR_.C001 acpi_perf1 powernow1 cpufreq1 unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.C002 unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.C003 acpi_button0 pnpinfo _HID=PNP0C0C _UID=0 at handle=\_SB_.PWRB pcib0 pnpinfo _HID=PNP0A08 _UID=1 at handle=\_SB_.PCI0 pci0 unknown pnpinfo vendor=0x10de device=0x02f4 subvendor=0x10de subdevice=0x02f0 class=0x05 at slot=0 function=0 unknown pnpinfo vendor=0x10de device=0x02fa subvendor=0x10de subdevice=0x02fa class=0x05 at slot=0 function=1 unknown pnpinfo vendor=0x10de device=0x02fe subvendor=0x10de subdevice=0x02fe class=0x05 at slot=0 function=2 unknown pnpinfo vendor=0x10de device=0x02f8 subvendor=0x10de subdevice=0x02f8 class=0x05 at slot=0 function=3 unknown pnpinfo vendor=0x10de device=0x02f9 subvendor=0x10de subdevice=0x02f9 class=0x05 at slot=0 function=4 unknown pnpinfo vendor=0x10de device=0x02ff subvendor=0x10de subdevice=0x02ff class=0x05 at slot=0 function=5 unknown pnpinfo vendor=0x10de device=0x02
Re: Buzzing snd_emu10kx enabled card with r206173
On 30/05/2010 08:31, Garrett Cooper wrote: > > Everything I saw there appeared sane (it would have been nice to grab > the -v output from kldstat, but that's ok...). Let's try doing the > following: > > 1. Add `options EMU_MTX_DEBUG' to your kernconf. > 2. Add set the sysctl: dev.emu10kx.0.debug=1 . > > Let's see if anything changes... > I've set SND_DEBUG and dev.emu10kx.0.debug=1. I'll listen to my sound output when I get home. > I'm going to try upgrading my kernel and I'll try these steps as well. > The locking between this driver and some other sound drivers isn't > exactly the same (interestingly enough this driver uses Giant locking > for some bits, while the ich one doesn't), and there were some past > bugs with other branches of *BSD's drivers related to pci bus > commands, etc; the other BSDs have dramatically different soundsystems > -- I assume the old school soundsystem, s.t. the issues are probably > not the same. > The part about PCI commands is very interesting. Could this be related to my PCI NIC (em) not working properly? Greetz, Mark signature.asc Description: OpenPGP digital signature
Re: Buzzing snd_emu10kx enabled card with r206173
On 05/30/10 08:31, Garrett Cooper wrote: > > Everything I saw there appeared sane (it would have been nice to grab > the -v output from kldstat, but that's ok...). Let's try doing the > following: > > 1. Add `options EMU_MTX_DEBUG' to your kernconf. > 2. Add set the sysctl: dev.emu10kx.0.debug=1 . > > Let's see if anything changes... > > Also, if you could provide some more hardware stats (say dmesg.boot > and/or devinfo -v) and version stats (I already know that you're > running amd64 from your kernel config) for the OS that would be > helpful as well. > > I'm going to try upgrading my kernel and I'll try these steps as well. > The locking between this driver and some other sound drivers isn't > exactly the same (interestingly enough this driver uses Giant locking > for some bits, while the ich one doesn't), and there were some past > bugs with other branches of *BSD's drivers related to pci bus > commands, etc; the other BSDs have dramatically different soundsystems > -- I assume the old school soundsystem, s.t. the issues are probably > not the same. > > Thanks, > -Garrett > I've update my kernel, put in the SND_DEBUG flag and set "dev.emu10kx.0.debug=1" Everything worked. Then I unset the flag. Everything still worked. Then I did a reboot without the flag in loader.conf Everything still worked! Weird... If it fails again i'll try to find something usefull in my loggings for you. Thanks for the help. Regards, Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
network deamons starting before network!
Hello, Since updating to 8.X I noticed that network services were started before the network was up! I use lagg failover configuration on both my FreeBSD boxes. First, boot fails on mounting my nfs-shares. After entering and exiting the "rescue" shell, the system boots as normal. uname -a FreeBSD mario 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #4: Fri Jun 18 07:46:01 CEST 2010 *...@mario:/usr/obj/usr/src/sys/mario amd64 What could I do to fix this? Here's an exerpt from /var/log/messages: Jun 18 09:10:25 ntpd[1376]: ntpd 4.2.4p5-a (1) Jun 18 09:10:25 kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 Jun 18 09:10:27 ntpd_initres[1412]: host name not found: yoshi Jun 18 09:10:27 kernel: nfe0: link state changed to UP Jun 18 09:10:27 kernel: lagg0: link state changed to UP Jun 18 09:10:27 kernel: nfe1: link state changed to UP Jun 18 09:10:27 ntpd_initres[1412]: couldn't resolve `yoshi', giving up on it Jun 18 09:10:28 dhclient: New Hostname (lagg0): mario Jun 18 09:10:28 dhclient: New IP Address (lagg0): 10.58.235.6 Jun 18 09:10:28 dhclient: New Subnet Mask (lagg0): 255.255.255.0 Jun 18 09:10:28 dhclient: New Broadcast Address (lagg0): 10.58.235.255 Jun 18 09:10:28 dhclient: New Routers (lagg0): 10.58.235.1 signature.asc Description: OpenPGP digital signature
Re: network deamons starting before network!
On 18/06/2010 10:26, Jeremy Chadwick wrote: > On Fri, Jun 18, 2010 at 09:34:24AM +0200, Mark Stapper wrote: > >> Hello, >> >> Since updating to 8.X I noticed that network services were started >> before the network was up! >> > This is common/normal. I wrote a script (still working on getting it > added to the base system) to deal with this issue. Please see: > > http://jdc.parodius.com/freebsd/netwait > > Drop this into /usr/local/etc/rc.d, chmod it 755, and read the > descriptions of the variables and add the appropriate settings to > rc.conf. > > Please be aware netwait_if only takes a single interface; you're using > lagg, so I hope that when your system boots whichever interface you pick > in netwait_if the one which you default to using. > > couldn't I use lagg0 on this parameter? thx btw :-) Regards, Mark signature.asc Description: OpenPGP digital signature
Re: network deamons starting before network!
On 06/18/10 12:20, Alfred Bartsch wrote: > Mark Stapper schrieb: > >> Hello, >> >> Since updating to 8.X I noticed that network services were started >> before the network was up! >> I use lagg failover configuration on both my FreeBSD boxes. >> First, boot fails on mounting my nfs-shares. >> After entering and exiting the "rescue" shell, the system boots as normal. >> > Hello, > > adding: > synchronous_dhclient="YES" > to /etc/rc.conf solved some similar issues for me. > The default behaviour of getting an IP via dhcp has changed. > I'll try that too. That would explain why I didn't have this problem on 7.2 I DO like the whole netwait idea though. But for me, the synchronous_dhclient flag should be sufficient I think. signature.asc Description: OpenPGP digital signature
Re: network deamons starting before network!
On 19/06/2010 11:06, Mark Stapper wrote: > On 06/18/10 12:20, Alfred Bartsch wrote: > >> Mark Stapper schrieb: >> >> >>> Hello, >>> >>> Since updating to 8.X I noticed that network services were started >>> before the network was up! >>> I use lagg failover configuration on both my FreeBSD boxes. >>> First, boot fails on mounting my nfs-shares. >>> After entering and exiting the "rescue" shell, the system boots as normal. >>> >>> >> Hello, >> >> adding: >> synchronous_dhclient="YES" >> to /etc/rc.conf solved some similar issues for me. >> The default behaviour of getting an IP via dhcp has changed. >> >> > I'll try that too. > That would explain why I didn't have this problem on 7.2 > I DO like the whole netwait idea though. > But for me, the synchronous_dhclient flag should be sufficient I think. > > Worked like a charm! Thank you again Regards, Mark signature.asc Description: OpenPGP digital signature
cone segmentation fault on 8.0-STABLE amd64
Hi all, I'm running cone on 8.0-STABLE. When I run the program for the first time it works like a charm! Cone then creates a configuration directory and conerc. When I run cone the second time it crashed with a segmentation fault. Then after removing the "OPTIONS" node from the config file cone starts again. When I go to the setup menu and hit "save" also crashes with segfault. Any ideas? Cheers, Mark conerc: x...@ signature.asc Description: OpenPGP digital signature
network probs rxcsum
Hi, I have two machines running FreeBSD amd64 8.0-Stable with custom kernels. My newer box has had troubles with ssh from day one. I hoped a kernel upgrade would help, but it didn't. When I'd ssh into the box ssh would exit with errors: Bad packet length xx Disconnecting: Packet corrupt. after issueing: "ifconfig em0 -rxcons" everything was stable again. First I figured it'd be a driver issue. However, I use the same NIC in my other box! What could be causing this problem? signature.asc Description: OpenPGP digital signature
Re: network probs rxcsum
On 19/05/2010 12:44, Jeremy Chadwick wrote: > On Wed, May 19, 2010 at 12:34:17PM +0200, Mark Stapper wrote: > >> I have two machines running FreeBSD amd64 8.0-Stable with custom kernels. >> My newer box has had troubles with ssh from day one. >> I hoped a kernel upgrade would help, but it didn't. >> When I'd ssh into the box ssh would exit with errors: >> Bad packet length xx >> Disconnecting: Packet corrupt. >> >> after issueing: "ifconfig em0 -rxcons" everything was stable again. >> First I figured it'd be a driver issue. However, I use the same NIC in >> my other box! >> What could be causing this problem? >> > I think you mean "-rxcsum", not "-rxcons". > > Could you please provide output from the following commands? Jack Vogel > will probably respond later about this, but said output would help him. > > - uname -a > - dmesg | grep em0 > - pciconf -lvc > > Thanks. > > Well, yes... something got garbled in my mind... I'll provide the outputs when I get home as the network connection just went down for no particilar reason... Greets, Mark signature.asc Description: OpenPGP digital signature
ZFS RAIDZ and atacontrol spindown settings
Good day, I am the proud user of a FreeBSD 7.2 AMD64 system housing, amongst other things, a data server. My "server"(It's called "Yoshi") runs FreeBSD from a mirrored system disc, and has a zfs RAIDZ array with 4 discs for bulky data. As it is a home server, and I work during the day, these four discs were spinning happily all day long without much use for them doing so. To save the world(and money) I issued the command "atacontrol spindown 1800" for all the discs in my array spinning them down after thirty minutes of idle spinning. So far so good, me very happy! However, when I access the array after the discs have been spun down, it spins up the discs one after the other... Mind you one AFTER the other, taking 4*9 seconds to do a "ls" command on my music directory. Content as I am with the smooth down- and upspinning of the disks, I would like it better if the four discs would spin up simultaneously. Thus my question: "Is it possible to \"group\" discs to be spun up together, or to issue a custom command upon upspinning of a disc such as to spin up other disks?" Thanks! Greetz, Mark signature.asc Description: OpenPGP digital signature
Re: ZFS RAIDZ and atacontrol spindown settings
Ivan Voras wrote: > 2009/7/21 Mark Stapper : > >> Ivan Voras wrote: >> >>> Mark Stapper wrote: >>> >>>> Good day, >>>> >>>> I am the proud user of a FreeBSD 7.2 AMD64 system housing, amongst other >>>> things, a data server. >>>> My "server"(It's called "Yoshi") runs FreeBSD from a mirrored system >>>> disc, and has a zfs RAIDZ array with 4 discs for bulky data. >>>> As it is a home server, and I work during the day, these four discs were >>>> spinning happily all day long without much use for them doing so. >>>> To save the world(and money) I issued the command "atacontrol spindown >>>> 1800" for all the discs in my array spinning them down after thirty >>>> minutes of idle spinning. >>>> So far so good, me very happy! However, when I access the array after >>>> the discs have been spun down, it spins up the discs one after the >>>> other... >>>> Mind you one AFTER the other, taking 4*9 seconds to do a "ls" command on >>>> my music directory. >>>> Content as I am with the smooth down- and upspinning of the disks, I >>>> would like it better if the four discs would spin up simultaneously. >>>> Thus my question: "Is it possible to \"group\" discs to be spun up >>>> together, or to issue a custom command upon upspinning of a disc such as >>>> to spin up other disks?" >>>> >>> Good question but the answer is probably no - it really only depends >>> on how ZFS accesses the drives; if it accesses them in sequence, you >>> can't change it. >>> >> I've been looking at writing a shell script which monitors >> /var/log/messages. >> something like: >> >> If last line in /var/log/messages is like "request while spun down. >> Starting." >>spinup disks >> >> couple of problems though, I should probably poll the kernel messages >> every second or so, but if I only check the last linee, I could miss the >> spinup message. >> I could count the number of lines in /var/log/messages and keep count of >> the number of lines i've seen. Problem with this approach is that it's >> not very efficient. >> So I was hoping there is a way to receive this kernel message directly. >> I am now thinking in the lines of a program which received a signal on >> new kernel messages available or something similar. >> >> Any thoughts? >> > > You could do what "tail -f" does and simply hook a kqueue to get new > messages from the /var/log/messages file. > I'll try that! thanks! signature.asc Description: OpenPGP digital signature
Re: ZFS RAIDZ and atacontrol spindown settings
Arnaud Houdelette wrote: > Mark Stapper a écrit : >> Ivan Voras wrote: >> >>> 2009/7/21 Mark Stapper : >>> >>>> Ivan Voras wrote: >>>> >>>>> Mark Stapper wrote: >>>>> >>>>>> Good day, >>>>>> >>>>>> I am the proud user of a FreeBSD 7.2 AMD64 system housing, >>>>>> amongst other >>>>>> things, a data server. >>>>>> My "server"(It's called "Yoshi") runs FreeBSD from a mirrored system >>>>>> disc, and has a zfs RAIDZ array with 4 discs for bulky data. >>>>>> As it is a home server, and I work during the day, these four >>>>>> discs were >>>>>> spinning happily all day long without much use for them doing so. >>>>>> To save the world(and money) I issued the command "atacontrol >>>>>> spindown >>>>>> 1800" for all the discs in my array spinning them down after thirty >>>>>> minutes of idle spinning. >>>>>> So far so good, me very happy! However, when I access the array >>>>>> after >>>>>> the discs have been spun down, it spins up the discs one after the >>>>>> other... >>>>>> Mind you one AFTER the other, taking 4*9 seconds to do a "ls" >>>>>> command on >>>>>> my music directory. >>>>>> Content as I am with the smooth down- and upspinning of the disks, I >>>>>> would like it better if the four discs would spin up simultaneously. >>>>>> Thus my question: "Is it possible to \"group\" discs to be spun up >>>>>> together, or to issue a custom command upon upspinning of a disc >>>>>> such as >>>>>> to spin up other disks?" >>>>>> >>>>> Good question but the answer is probably no - it really only depends >>>>> on how ZFS accesses the drives; if it accesses them in sequence, you >>>>> can't change it. >>>>> >>>> I've been looking at writing a shell script which monitors >>>> /var/log/messages. >>>> something like: >>>> >>>> If last line in /var/log/messages is like "request while spun down. >>>> Starting." >>>>spinup disks >>>> >>>> couple of problems though, I should probably poll the kernel messages >>>> every second or so, but if I only check the last linee, I could >>>> miss the >>>> spinup message. >>>> I could count the number of lines in /var/log/messages and keep >>>> count of >>>> the number of lines i've seen. Problem with this approach is that it's >>>> not very efficient. >>>> So I was hoping there is a way to receive this kernel message >>>> directly. >>>> I am now thinking in the lines of a program which received a signal on >>>> new kernel messages available or something similar. >>>> >>>> Any thoughts? >>>> >>> You could do what "tail -f" does and simply hook a kqueue to get new >>> messages from the /var/log/messages file. >>> >> I'll try that! thanks! >> >> > As I get quite the same issue with a 4 disk raidz pool, could you > please tell me the result of your tries ? which command do you use to > force the disks to spin up ? > > Thanks I have been using a shell script containing: #!/bin.sh dd if=/dev/ad4 of=/dev/null count=1& dd if=/dev/ad6 of=/dev/null count=1& dd if=/dev/ad8 of=/dev/null count=1& dd if=/dev/ad10 of=/dev/null count=1& signature.asc Description: OpenPGP digital signature
Re: ZFS RAIDZ and atacontrol spindown settings
Arnaud Houdelette wrote: > Mark Stapper wrote: >> Arnaud Houdelette wrote: >> >>> Mark Stapper a écrit : >>> >>>> Ivan Voras wrote: >>>> >>>> >>>>> 2009/7/21 Mark Stapper : >>>>> >>>>>> Ivan Voras wrote: >>>>>> >>>>>>> Mark Stapper wrote: >>>>>>> >>>>>>>> Good day, >>>>>>>> >>>>>>>> I am the proud user of a FreeBSD 7.2 AMD64 system housing, >>>>>>>> amongst other >>>>>>>> things, a data server. >>>>>>>> My "server"(It's called "Yoshi") runs FreeBSD from a mirrored >>>>>>>> system >>>>>>>> disc, and has a zfs RAIDZ array with 4 discs for bulky data. >>>>>>>> As it is a home server, and I work during the day, these four >>>>>>>> discs were >>>>>>>> spinning happily all day long without much use for them doing so. >>>>>>>> To save the world(and money) I issued the command "atacontrol >>>>>>>> spindown >>>>>>>> 1800" for all the discs in my array spinning them down after >>>>>>>> thirty >>>>>>>> minutes of idle spinning. >>>>>>>> So far so good, me very happy! However, when I access the array >>>>>>>> after >>>>>>>> the discs have been spun down, it spins up the discs one after the >>>>>>>> other... >>>>>>>> Mind you one AFTER the other, taking 4*9 seconds to do a "ls" >>>>>>>> command on >>>>>>>> my music directory. >>>>>>>> Content as I am with the smooth down- and upspinning of the >>>>>>>> disks, I >>>>>>>> would like it better if the four discs would spin up >>>>>>>> simultaneously. >>>>>>>> Thus my question: "Is it possible to \"group\" discs to be >>>>>>>> spun up >>>>>>>> together, or to issue a custom command upon upspinning of a disc >>>>>>>> such as >>>>>>>> to spin up other disks?" >>>>>>>> >>>>>>> Good question but the answer is probably no - it really only >>>>>>> depends >>>>>>> on how ZFS accesses the drives; if it accesses them in sequence, >>>>>>> you >>>>>>> can't change it. >>>>>>> >>>>>> I've been looking at writing a shell script which monitors >>>>>> /var/log/messages. >>>>>> something like: >>>>>> >>>>>> If last line in /var/log/messages is like "request while spun down. >>>>>> Starting." >>>>>>spinup disks >>>>>> >>>>>> couple of problems though, I should probably poll the kernel >>>>>> messages >>>>>> every second or so, but if I only check the last linee, I could >>>>>> miss the >>>>>> spinup message. >>>>>> I could count the number of lines in /var/log/messages and keep >>>>>> count of >>>>>> the number of lines i've seen. Problem with this approach is that >>>>>> it's >>>>>> not very efficient. >>>>>> So I was hoping there is a way to receive this kernel message >>>>>> directly. >>>>>> I am now thinking in the lines of a program which received a >>>>>> signal on >>>>>> new kernel messages available or something similar. >>>>>> >>>>>> Any thoughts? >>>>>> >>>>> You could do what "tail -f" does and simply hook a kqueue to get new >>>>> messages from the /var/log/messages file. >>>>> >>>> I'll try that! thanks! >>>> >>>> >>> As I get quite the same issue with a 4 disk raidz pool, could you >>> please tell me the result of your tries ? which command do you use to &g
Re: Cannot rm files when ZFS is full
Christian Walther wrote: > 2009/7/29 grarpamp : > >> One week old build... >> >> # df -i . >> Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted >> on >> ram01/mnt1 239465344 239465344 0 100% 13163 0 100% /mnt1 >> # ls -aliT zero >> 20797 -rw-r--r-- 1 user user 43515904 Jul 28 23:20:57 2009 zero >> # rm -f zero >> rm: zero: No space left on device >> # :> zero >> cannot create zero: File exists >> # cp /dev/null zero >> overwrite zero? (y/n [n]) y >> # ls -aliT zero >> 20797 -rw-rw-rw- 1 root wheel 0 Jul 28 23:25:17 2009 zero >> # rm -f zero >> [gone] >> > > > this is a known problem with the current version of ZFS. Due to the > way ZFS handles access to the data it stores, even a rm causes a > write, which requires some additional disk space in the beginning: > Instead of simply unlinking what should be removed ZFS creates another > tree without the removed data. Only if this new tree has been entirely > written to disk the old information is removed. This is a rather rough > explanation and probably not entirely correct, but I hope it suffices. > Only hope: Make sure that not all disk space is used. > > Christian > Indeed, if by some coincident (like a growing logfile) every single byte is used, even the copy action might fail... To prevent this you could set the maximum size of all partitions in your pool so that the sum of them is smaller then the size of your pool. Just a thought. Greetz, Mark signature.asc Description: OpenPGP digital signature
Re: ZFS RAIDZ and atacontrol spindown settings
Arnaud Houdelette wrote: > Mark Stapper wrote: >> Arnaud Houdelette wrote: >> >>> Mark Stapper a écrit : >>> >>>> Ivan Voras wrote: >>>> >>>> >>>>> 2009/7/21 Mark Stapper : >>>>> >>>>>> Ivan Voras wrote: >>>>>> >>>>>>> Mark Stapper wrote: >>>>>>> >>>>>>>> Good day, >>>>>>>> >>>>>>>> I am the proud user of a FreeBSD 7.2 AMD64 system housing, >>>>>>>> amongst other >>>>>>>> things, a data server. >>>>>>>> My "server"(It's called "Yoshi") runs FreeBSD from a mirrored >>>>>>>> system >>>>>>>> disc, and has a zfs RAIDZ array with 4 discs for bulky data. >>>>>>>> As it is a home server, and I work during the day, these four >>>>>>>> discs were >>>>>>>> spinning happily all day long without much use for them doing so. >>>>>>>> To save the world(and money) I issued the command "atacontrol >>>>>>>> spindown >>>>>>>> 1800" for all the discs in my array spinning them down after >>>>>>>> thirty >>>>>>>> minutes of idle spinning. >>>>>>>> So far so good, me very happy! However, when I access the array >>>>>>>> after >>>>>>>> the discs have been spun down, it spins up the discs one after the >>>>>>>> other... >>>>>>>> Mind you one AFTER the other, taking 4*9 seconds to do a "ls" >>>>>>>> command on >>>>>>>> my music directory. >>>>>>>> Content as I am with the smooth down- and upspinning of the >>>>>>>> disks, I >>>>>>>> would like it better if the four discs would spin up >>>>>>>> simultaneously. >>>>>>>> Thus my question: "Is it possible to \"group\" discs to be >>>>>>>> spun up >>>>>>>> together, or to issue a custom command upon upspinning of a disc >>>>>>>> such as >>>>>>>> to spin up other disks?" >>>>>>>> >>>>>>> Good question but the answer is probably no - it really only >>>>>>> depends >>>>>>> on how ZFS accesses the drives; if it accesses them in sequence, >>>>>>> you >>>>>>> can't change it. >>>>>>> >>>>>> I've been looking at writing a shell script which monitors >>>>>> /var/log/messages. >>>>>> something like: >>>>>> >>>>>> If last line in /var/log/messages is like "request while spun down. >>>>>> Starting." >>>>>>spinup disks >>>>>> >>>>>> couple of problems though, I should probably poll the kernel >>>>>> messages >>>>>> every second or so, but if I only check the last linee, I could >>>>>> miss the >>>>>> spinup message. >>>>>> I could count the number of lines in /var/log/messages and keep >>>>>> count of >>>>>> the number of lines i've seen. Problem with this approach is that >>>>>> it's >>>>>> not very efficient. >>>>>> So I was hoping there is a way to receive this kernel message >>>>>> directly. >>>>>> I am now thinking in the lines of a program which received a >>>>>> signal on >>>>>> new kernel messages available or something similar. >>>>>> >>>>>> Any thoughts? >>>>>> >>>>> You could do what "tail -f" does and simply hook a kqueue to get new >>>>> messages from the /var/log/messages file. >>>>> >>>> I'll try that! thanks! >>>> >>>> >>> As I get quite the same issue with a 4 disk raidz pool, could you >>> please tell me the result of your tries ? which command do you use to >&g
Re: zfs on gmirror slice
Miroslav Lachman wrote: > Maciej Jan Broniarz wrote: >> 2009/9/1 Thomas Backman : >> >>> On Sep 1, 2009, at 4:04 PM, Maciej Jan Broniarz wrote: >>> >>> >>> I'm not familiar with gmirror, but it'd be a way better idea to >>> mirror it >>> using ZFS if possible - that way you get self-healing and stuff like >>> that, >>> which you won't if ZFS doesn't have a mirror/RAIDZ setup, but only >>> sees a >>> single slice. >>> >> >> >> I would like to do so. I have to disks (ad4 and ad5). Is it possible >> to create two slices on both disks (eg ad4s1 and ad4s2 for ad4). >> Then to create gmirror on ad4s1, install freebsd on it so it would >> boot from it. Then, after having my system running to create zfs >> mirror from ad4s2 and ad5s2? > > Yes, I am using it this way: > > r...@cage ~/# gmirror status >NameStatus Components > mirror/gms1 COMPLETE ad4s1 >ad6s1 > > > r...@cage ~/# zpool status > pool: tank > state: ONLINE > scrub: none requested > config: > > NAMESTATE READ WRITE CKSUM > tankONLINE 0 0 0 > mirrorONLINE 0 0 0 > ad4s2 ONLINE 0 0 0 > ad6s2 ONLINE 0 0 0 > > errors: No known data errors > > > r...@cage ~/# zpool list > NAMESIZEUSED AVAILCAP HEALTH ALTROOT > tank444G353G 91.2G79% ONLINE - > > > gmirror gms1 is for system files, ports etc. zpool (444GB) is for jails > > Miroslav Lachman > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" Hello, I'm quite surprised by your setup, as you are using two mechanisms to accomplish the exact same thing: data replication. If you want two slices of toast do you use a toaster for one, and an oven for the other? My advice to you: either use zfs or gmirror to realize redundancy. Of course, zfs provides far more flexibility then UFS. However, as mentioned, booting from ZFS isn't something sysinstall can setup for you. Besides, updating a zfs filesystem which you are running from is next to impossible. And since ZFS is still under heavy development, you will want to update your zfs version every now and then. So, i would recommend setting up gmirror to mirror your whole disks, install the base system(boot and "world") on a small UFS slice, and use the rest of the disc as zfs slice. If you feel comfortable enough running your entire system on zfs, you could use a mirrored zpool to boot from. Takes a little more efford, but is more uniform. Updating zfs will be a pain though. You would have to boot from another filesystem to be able to update your root filesystem. If you'll be reinstalling your system, you might want to check out FreeBSD 8 because zfs boot support is better. Hope it helps. Greetz, Mark signature.asc Description: OpenPGP digital signature
Re: zfs on gmirror slice
Emil Mikulic wrote: > On Wed, Sep 02, 2009 at 09:20:21AM +0200, Mark Stapper wrote: > >> updating a zfs filesystem which you are running from is next to >> impossible. >> > > [citation needed] :) > Well, to update your zfs filesystem version, the filesystem is first unmounted, then updated, and then mounted again. citation coming up! # umount / umount: unmount of / failed: Invalid argument > >> So, i would recommend setting up gmirror to mirror your whole disks, >> install the base system(boot and "world") on a small UFS slice, and use >> the rest of the disc as zfs slice. >> > > As Thomas Backman pointed out, this means you won't get self-healing. > self-healing sounds very nice, but with mirrorring you have data on two discs, so in that case there no "healing" involved, it's just checksumming and reading the non-corrupted copy. From the gmirror manpage: "All operations like failure detection, stale component detection, rebuild of stale components, etc. are also done automatically." This would indicate the same functionality, with a much less fancy name. However, i have not tested it the way they demonstrate zfs's "self-healing" property. I might, if I get the time to run it in a virtual machine one of these days.. > I don't know if a ZFS mirror performs smarter disk access scheduling > than gmirror. Someone oughta measure. ;) > NCQ should help here, but still, very interesting. gmirror is fast though. I've even heard it's faster than software RAID1/ataraid. (not confirmed). Even if this is true, running zfs on top of gmirror probably isn't faster then running zfs with a mirrored pool. signature.asc Description: OpenPGP digital signature
Re: zfs on gmirror slice
Thomas Backman wrote: > On Sep 2, 2009, at 10:27 AM, Mark Stapper wrote: > >> > Nothing a LiveCD or something to that regard can't handle. Obviously > this doesn't work for everyone, but it should for many. Actually it won't because updating zfs comes with updating your world. After updating you world, you will be running a newer ZFS version then the one that come with the RELEASE install, hence the need to update your zfs filesystems. Incidentally, the livefs CD contains the "old" zfs version. You see where I'm going? You could, of course, copy the base system to a USB drive, boot from it, and so sidestep the whole "can't unmount root" problem, but it's hard to insert a USB device over ssh... ... ... >> self-healing sounds very nice, but with mirrorring you have data on two >> discs, so in that case there no "healing" involved, it's just >> checksumming and reading the non-corrupted copy. >> From the gmirror manpage: "All operations like failure detection, stale >> component detection, rebuild of stale components, etc. are also done >> automatically." >> This would indicate the same functionality, with a much less fancy name. >> However, i have not tested it the way they demonstrate zfs's >> "self-healing" property. >> I might, if I get the time to run it in a virtual machine one of these >> days.. > If ZFS finds a corrupted copy and a non-corrupted one in a mirrored > ZFS pool, it will repair the damage so that both copies are valid, so > yes, self-healing will indeed occur. :) I'm feeling Shakespearean again... My point was that I find "self-healing" too magic sounding. While indeed it means:"Automatic data error detection and rebuilding" or something along those lines. We don't call the automatic remapping of bad sectors in HDD's "self-healing" do we? Alas, I must admit that on file-system level, some "healing" does take place. signature.asc Description: OpenPGP digital signature
Re: Subscribe to your mailing list(off topic)
Jeffrey Goldberg wrote: > On Aug 31, 2009, at 1:33 PM, Szára György wrote: > >> I had some nuisance when after implementation booting 7.2 release. It >> denied me to boot the once installed release. > > I don't understand what you are saying. Are you saying that once you > installed 7.2 the system wouldn't boot? > > Azt mondod, hogy nem boot-ol az 7.2es insztelació utan? > >> Further I have very strong annoyance implementing the Localisation.We >> need of accent over voayels aniway. >> Best regards Gyorgy Szara. > > Considering your name, I understand why you need the accent marks. > > Have you looked at the instructions in chapter 23 of the handbook? > > http://www.freebsd.org/doc/hu/books/handbook/l10n.html > > Minden jót kivánok > > -jeff > Just off topic.. but.. Magyar? Egészségedre! Mark signature.asc Description: OpenPGP digital signature
