Re: FreeBSD 8.2 Release, ZFS + Samba, running out of memory
I only connect to the BSD system via ssh at the moment, there is no keyboard attached. The ssh shell running "top" doesn't update anymore and doesn't take any input. A new ssh session is not possible. Pressing the power button once does not shut down the machine, i have to keep it pressed for several seconds to power down hard. I will try out disabling "sendfile" and, if i can manage, also try out the patch. This would be my first kernel patch and compilation, so it might take a while to learn. :) Would i run the risk of loosing the patch when running "freebsd-update"? Will the patch be provided by "freebsd-update" at some point? Thank you all for your advice, Henner Heck Am 22.02.2011 23:43, schrieb Jeremy Chadwick: > >> *smb.conf* (a bit anonymized) >> >> [global] >> use sendfile = true > Set this to "false" and the problem might go away. You can try some of > the patches others have recommended as well (which will permit you to > use sendfile going forward), but if you don't want to deal with patches, > the workaround should be fine. > > If you still experience issues after that, possibly some loader.conf > tuning for ZFS is needed. > > Also, one question: when you say "freezes", do you mean "completely > locks up hard" or "the system seems alive but seems to be spending all > of its CPU time doing something else"? Try hitting NumLock on the > system's keyboard to see if the LED toggles on/off; if it does, the > system isn't frozen, but is catatonic to some degree. > ___ 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"
Re: FreeBSD 8.2 Release, ZFS + Samba, running out of memory
On Tue, Feb 22, 2011 at 10:55:37PM +0100, Henner Heck wrote: > i experience freezing of my FreeBSD machine when performing certain > operations > on a Samba share. > > Technical info: > - FreeBSD 8.2 Release 64 Bit (it also happened with 8.2 RC3) > - Samba 3.5.6.1 > - Athlon II Quadcore, 4 GB Ram > - 1 SSD with a ZFS pool (No.0) containing the FreeBSD system > - 12x2TB RaidZ2 pool (No.1) for data, created on 12 GEOM eli encrypted > partitions on 12 disks, > shared to a Windows 7 PC with Samba, > 8 of the disks are attached to 2 Marvell SATA controllers, 4 to the > onboard controller > - ZPool v15, ZFS v4 > > Scenarios (checked using top): > > A: > When copying files from one directory in pool 1 to another, the free > memory drops from > about 3700M to abaout 200M in the process, but seems to stabilize then. > > B: > When copying the files onto a Windows machine using the Samba share, > the free memory seems to stabilize at about 100M. > > C: > When computing a hashvalue of files from the share on Windows or doing a > binary compare to copies of the files stored on the Windows PC (using > Total Commander), > the free memory on the FreeBSD machine drops even lower and shortly > after the BSD system freezes. > Here is the last top output i got via ssh: > > ... > > Does anyone have advice on how to get rid of this problem? > > ... > > *smb.conf* (a bit anonymized) > > [global] > use sendfile = true Set this to "false" and the problem might go away. You can try some of the patches others have recommended as well (which will permit you to use sendfile going forward), but if you don't want to deal with patches, the workaround should be fine. If you still experience issues after that, possibly some loader.conf tuning for ZFS is needed. Also, one question: when you say "freezes", do you mean "completely locks up hard" or "the system seems alive but seems to be spending all of its CPU time doing something else"? Try hitting NumLock on the system's keyboard to see if the LED toggles on/off; if it does, the system isn't frozen, but is catatonic to some degree. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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"
Re: NFS client over udp
> --- On Tue, 2/22/11, Rick Macklem wrote: > > > From: Rick Macklem > > Subject: Re: NFS client over udp > > To: "Kirill Yelizarov" > > Cc: freebsd-stable@freebsd.org > > Date: Tuesday, February 22, 2011, 2:10 AM > > > --- On Sun, 2/20/11, Rick > > Macklem > > wrote: > > > > > > > From: Rick Macklem > > > > Subject: Re: NFS client over udp > > > > To: "Kirill Yelizarov" > > > > Cc: freebsd-stable@freebsd.org > > > > Date: Sunday, February 20, 2011, 9:02 PM > > > > > --- On Fri, 2/18/11, Kirill > > > > Yelizarov > > > > > > > On Fri, Feb 18, 2011 at > > 05:27:00AM > > > > > > > -0800, Kirill Yelizarov wrote: > > > > > > > > I have a reproducible memory > > leak when > > > > using nfs > > > > > > > client with an old > > > > > > > > nfs server > > > > > > > > > > and mbufs used > > > > > 8193/1722/9915 mbufs in use > > (current/cache/total) > > > > > 8192/1264/9456/25600 mbuf clusters in use > > > > (current/cache/total/max) > > > > > 8192/605 mbuf+clusters out of packet > > secondary zone in > > > > use > > > > > (current/cache) > > > > > 0/768/768/12800 4k (page size) jumbo > > clusters in use > > > > > (current/cache/total/max) > > > > > 0/0/0/6400 9k jumbo clusters in use > > > > (current/cache/total/max) > > > > > 0/0/0/3200 16k jumbo clusters in use > > > > (current/cache/total/max) > > > > > 18432K/6030K/24462K bytes allocated to > > network > > > > (current/cache/total) > > > > > 0/0/0 requests for mbufs denied > > > > (mbufs/clusters/mbuf+clusters) > > > > > 0/0/0 requests for jumbo clusters denied > > (4k/9k/16k) > > > > > 0/0/0 sfbufs in use (current/peak/max) > > > > > 0 requests for sfbufs denied > > > > > 0 requests for sfbufs delayed > > > > > 0 requests for I/O initiated by sendfile > > > > > 0 calls to protocol drain routines > > > > > > > > > > Kirill > > > > > > > > > You could try the attached patch. It fixes the > > only places > > > > in the > > > > client side krpc over udp that seems mights cause > > a leak. I > > > > have no > > > > idea if it will help, since these cases should > > rarely, if > > > > ever, > > > > happen in practice. > > > > > > > > Please let us know if you have the chance to try > > the patch > > > > and > > > > whether or not it helped. > > > > > > > > rick > > > > > > > Rick, i tried your patch. Fortunately it didn't help > > me. There are no > > > warnings on console and memory is climbing up during > > syncs and not > > > freed later. I'll try to switch to tcp this evening. > > Thanks for help > > > > > I'll assume that's unfortunately;-) Since the two cases > > patched probably > > never happen, I'm not surprised. > > > > The only other thing I can think of that you could try is > > switching to > > the experimental client. This would identify if the bug is > > in the regular > > client or somewhere further down in the rpc transport. > > > > The mount command would look something like: > > # mount -t newnfs -o nfsv3,udp : > > > > > I added options NFSCL to my kernel and tried to mount. mount shows > everything is ok: > 192.168.0.35:/home on /mnt (newnfs) > but when i try to cd /mnt i get permission denied > my export allow root and everything is done as root. What am i doing > wrong? > Try adding the "resvport" option. I don't think it's a default for the experimental client at this time. (I have a series of patches for the client that will go into head in April that brings it in line with the regular client, including same default mount options.) rick ___ 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"
Re: FreeBSD 8.2 Release, ZFS + Samba, running out of memory
There looks like a known bug of not activating memory pages if using sendfile(2). This was fixed by kib@ in revision 218795 of stable/8. Please try the following patch and report the result: http://people.freebsd.org/~mm/patches/releng_8_2/218795.zfs.patch Dňa 22.02.2011 22:55, Henner Heck wrote / napísal(a): > > Hello, > > i experience freezing of my FreeBSD machine when performing certain > operations > on a Samba share. > > Technical info: > - FreeBSD 8.2 Release 64 Bit (it also happened with 8.2 RC3) > - Samba 3.5.6.1 > - Athlon II Quadcore, 4 GB Ram > - 1 SSD with a ZFS pool (No.0) containing the FreeBSD system > - 12x2TB RaidZ2 pool (No.1) for data, created on 12 GEOM eli encrypted > partitions on 12 disks, > shared to a Windows 7 PC with Samba, > 8 of the disks are attached to 2 Marvell SATA controllers, 4 to the > onboard controller > - ZPool v15, ZFS v4 > > Scenarios (checked using top): > > A: > When copying files from one directory in pool 1 to another, the free > memory drops from > about 3700M to abaout 200M in the process, but seems to stabilize then. > > B: > When copying the files onto a Windows machine using the Samba share, > the free memory seems to stabilize at about 100M. > > C: > When computing a hashvalue of files from the share on Windows or doing a > binary compare to copies of the files stored on the Windows PC (using > Total Commander), > the free memory on the FreeBSD machine drops even lower and shortly > after the BSD system freezes. ___ 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"
Re: FreeBSD 8.2 Release, ZFS + Samba, running out of memory
On Tue, Feb 22, 2011 at 10:55:37PM +0100, Henner Heck wrote: > > Hello, > > i experience freezing of my FreeBSD machine when performing certain > operations > on a Samba share. > > Technical info: > - FreeBSD 8.2 Release 64 Bit (it also happened with 8.2 RC3) > - Samba 3.5.6.1 > - Athlon II Quadcore, 4 GB Ram > - 1 SSD with a ZFS pool (No.0) containing the FreeBSD system > - 12x2TB RaidZ2 pool (No.1) for data, created on 12 GEOM eli encrypted > partitions on 12 disks, > shared to a Windows 7 PC with Samba, > 8 of the disks are attached to 2 Marvell SATA controllers, 4 to the > onboard controller > - ZPool v15, ZFS v4 > > Scenarios (checked using top): > > A: > When copying files from one directory in pool 1 to another, the free > memory drops from > about 3700M to abaout 200M in the process, but seems to stabilize then. > > B: > When copying the files onto a Windows machine using the Samba share, > the free memory seems to stabilize at about 100M. > > C: > When computing a hashvalue of files from the share on Windows or doing a > binary compare to copies of the files stored on the Windows PC (using > Total Commander), > the free memory on the FreeBSD machine drops even lower and shortly > after the BSD system freezes. > Here is the last top output i got via ssh: > > /last pid: 1328; load averages: 4.53, 2.23, 0.99up 0+00:04:39 > 22:07:50 > 263 processes: 43 running, 201 sleeping, 19 waiting > CPU: 0.9% user, 0.0% nice, 23.1% system, 4.2% interrupt, 71.9% idle > Mem: 720K Active, 516M Wired, 144K Cache, 320K Buf, *39M Free* > Swap: 4096M Total, 12M Used, 4084M Free, 3008K In, 5124K Out > > PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND >11 root4 171 ki31 0K64K RUN 0 15:54 303.61% idle > 1321 root1 520 27812K 704K swread 1 0:24 14.26% smbd >12 root 19 -60- 0K 304K WAIT0 0:21 12.45% intr >16 root1 48- 0K16K psleep 2 0:01 3.76% > pagedaemon > 3 root1 -8- 0K16K RUN 0 0:06 3.27% g_up > 4 root1 -8- 0K16K - 3 0:05 2.69% g_down > 0 root 108 -80 0K 1712K - 0 1:02 1.86% kernel > 8 root6 -8- 0K88K tx->tx 1 0:00 1.27% zfskern > 1268 root1 44- 0K16K geli:w 1 0:03 0.98% > g_eli[1] gpt > 1225 root1 45- 0K16K RUN 3 0:02 0.98% > g_eli[3] gpt > 1267 root1 44- 0K16K geli:w 0 0:02 0.98% > g_eli[0] gpt > 1237 root1 44- 0K16K RUN 0 0:02 0.88% > g_eli[0] gpt > 1214 root1 44- 0K16K RUN 2 0:02 0.88% > g_eli[2] gpt > 1244 root1 44- 0K16K RUN 2 0:02 0.78% > g_eli[2] gpt > 1243 root1 44- 0K16K RUN 1 0:02 0.78% > g_eli[1] gpt > 1212 root1 44- 0K16K RUN 0 0:02 0.78% > g_eli[0] gpt > 1215 root1 44- 0K16K RUN 3 0:02 0.78% > g_eli[3] gpt > 1213 root1 44- 0K16K RUN 1 0:02 0.78% > g_eli[1] gpt > 1240 root1 44- 0K16K RUN 3 0:02 0.78% > g_eli[3] gpt > 1217 root1 44- 0K16K RUN 0 0:02 0.78% > g_eli[0] gpt > 1242 root1 44- 0K16K RUN 0 0:02 0.68% > g_eli[0] gpt > 1238 root1 44- 0K16K RUN 1 0:02 0.68% > g_eli[1] gpt > 1248 root1 44- 0K16K RUN 1 0:02 0.68% > g_eli[1] gpt > 1252 root1 44- 0K16K RUN 0 0:02 0.68% > g_eli[0] gpt > 1249 root1 44- 0K16K RUN 2 0:02 0.68% > g_eli[2] gpt > 1269 root1 44- 0K16K geli:w 2 0:02 0.68% > g_eli[2] gpt/ > > It looks like a caching problem to me, but i don't know how to fix it. > I am also a bit confused, since i don't see an obvious difference > between scenario B and C. > I had a similar setup with 5 disks RaidZ1 and Samba running on 8.1 Release, > and never experienced such a freeze. > > Does anyone have advice on how to get rid of this problem? Try the patch from rev. 218795. If it indeed help, we would need an errara notice. pgp337czssbUY.pgp Description: PGP signature
FreeBSD 8.2 Release, ZFS + Samba, running out of memory
Hello, i experience freezing of my FreeBSD machine when performing certain operations on a Samba share. Technical info: - FreeBSD 8.2 Release 64 Bit (it also happened with 8.2 RC3) - Samba 3.5.6.1 - Athlon II Quadcore, 4 GB Ram - 1 SSD with a ZFS pool (No.0) containing the FreeBSD system - 12x2TB RaidZ2 pool (No.1) for data, created on 12 GEOM eli encrypted partitions on 12 disks, shared to a Windows 7 PC with Samba, 8 of the disks are attached to 2 Marvell SATA controllers, 4 to the onboard controller - ZPool v15, ZFS v4 Scenarios (checked using top): A: When copying files from one directory in pool 1 to another, the free memory drops from about 3700M to abaout 200M in the process, but seems to stabilize then. B: When copying the files onto a Windows machine using the Samba share, the free memory seems to stabilize at about 100M. C: When computing a hashvalue of files from the share on Windows or doing a binary compare to copies of the files stored on the Windows PC (using Total Commander), the free memory on the FreeBSD machine drops even lower and shortly after the BSD system freezes. Here is the last top output i got via ssh: /last pid: 1328; load averages: 4.53, 2.23, 0.99up 0+00:04:39 22:07:50 263 processes: 43 running, 201 sleeping, 19 waiting CPU: 0.9% user, 0.0% nice, 23.1% system, 4.2% interrupt, 71.9% idle Mem: 720K Active, 516M Wired, 144K Cache, 320K Buf, *39M Free* Swap: 4096M Total, 12M Used, 4084M Free, 3008K In, 5124K Out PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 11 root4 171 ki31 0K64K RUN 0 15:54 303.61% idle 1321 root1 520 27812K 704K swread 1 0:24 14.26% smbd 12 root 19 -60- 0K 304K WAIT0 0:21 12.45% intr 16 root1 48- 0K16K psleep 2 0:01 3.76% pagedaemon 3 root1 -8- 0K16K RUN 0 0:06 3.27% g_up 4 root1 -8- 0K16K - 3 0:05 2.69% g_down 0 root 108 -80 0K 1712K - 0 1:02 1.86% kernel 8 root6 -8- 0K88K tx->tx 1 0:00 1.27% zfskern 1268 root1 44- 0K16K geli:w 1 0:03 0.98% g_eli[1] gpt 1225 root1 45- 0K16K RUN 3 0:02 0.98% g_eli[3] gpt 1267 root1 44- 0K16K geli:w 0 0:02 0.98% g_eli[0] gpt 1237 root1 44- 0K16K RUN 0 0:02 0.88% g_eli[0] gpt 1214 root1 44- 0K16K RUN 2 0:02 0.88% g_eli[2] gpt 1244 root1 44- 0K16K RUN 2 0:02 0.78% g_eli[2] gpt 1243 root1 44- 0K16K RUN 1 0:02 0.78% g_eli[1] gpt 1212 root1 44- 0K16K RUN 0 0:02 0.78% g_eli[0] gpt 1215 root1 44- 0K16K RUN 3 0:02 0.78% g_eli[3] gpt 1213 root1 44- 0K16K RUN 1 0:02 0.78% g_eli[1] gpt 1240 root1 44- 0K16K RUN 3 0:02 0.78% g_eli[3] gpt 1217 root1 44- 0K16K RUN 0 0:02 0.78% g_eli[0] gpt 1242 root1 44- 0K16K RUN 0 0:02 0.68% g_eli[0] gpt 1238 root1 44- 0K16K RUN 1 0:02 0.68% g_eli[1] gpt 1248 root1 44- 0K16K RUN 1 0:02 0.68% g_eli[1] gpt 1252 root1 44- 0K16K RUN 0 0:02 0.68% g_eli[0] gpt 1249 root1 44- 0K16K RUN 2 0:02 0.68% g_eli[2] gpt 1269 root1 44- 0K16K geli:w 2 0:02 0.68% g_eli[2] gpt/ It looks like a caching problem to me, but i don't know how to fix it. I am also a bit confused, since i don't see an obvious difference between scenario B and C. I had a similar setup with 5 disks RaidZ1 and Samba running on 8.1 Release, and never experienced such a freeze. Does anyone have advice on how to get rid of this problem? Best regards, Henner Heck *Config files* -- *loader.conf* ahci_load="YES" hw.hptrr.attach_generic=0 mvs_load="YES" aio_load="YES" kern.geom.label.gptid.enable=0 geom_label_load="YES" geom_eli_load="YES" zfs_load="YES" hint.acpi_throttle.0.disabled=1 hw.pci.do_power_nodriver=3 vfs.root.mountfrom="zfs:pool0/ROOT/freebsd" *rc.conf* (a bit anonymized) defaultrouter="xxx.xxx.xxx.xxx" hostname="hostname" ifconfig_em0="inet xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx" keymap="german.iso" zfs_enable="YES" sshd_enable="YES" geli_autodetach="NO" samba_enable="YES" powerd_enable="YES" *sysctl.conf* No active entries *smb.conf* (a bit anonymized) [global] workgroup = AG server string = Praetoria log file = /var/log/log.%m log level = 0 max log size = 50 security = user encrypt passwords = yes use sendfile = true min receivefile size = 131072 aio read size = 16384 aio write size = 16384 #needed for aio to work write cache size = 0 [user1] comment = Share for user user1 pat
Re: Problem with ipfw and libalias on 8.2-PRERELEASE
On 02/22/2011 04:28, Sergey Kandaurov wrote: On 22 February 2011 00:30, Etienne Robillard wrote: Hi, I'm unable to load the ipfw module in 8.2-PRELEASE. i think this may be due to ABI changes at the kernel level. , $ sudo kldload /boot/kernel/ipfw.ko $ dmesg ... KLD ipfw.ko: depends on libalias - not available or version mismatch linker_load_file: Unsupported file type $ uname -a FreeBSD marina.localdomain 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #1: Wed Feb 16 03:38:23 EST 2011 root@:/usr/local/freebsd8/src/sys/amd64/compile/GENERIC.ndebug amd64 could there be a more precise explanation? In recent 8.x you first need to kldload libalias.ko. It was broken in 8 since MFC r200636 (and still broken in head), where ipfw.ko includes ipfw_nat, which depends on libalias. I think either ipfw should un-include ipfw_nat stuff, or pollute self more and take explicit dependency on libalias. Thanks that fixed it. I recall having tried to manually load libalias.ko but after a full buildworld it works fine. ___ 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"
Re: Freebsd-update and release candidates
On 01/-10/-28163 20:59, Renato Botelho wrote: On Tue, Feb 22, 2011 at 11:04 AM, Svein Skogen wrote: I'm in the process of setting up a small network of FreeBSD installations. My plan (this time) is to keep them on branches available to freebsd-update, instead of depending on source being checked out from CVS. However, I'm a wee bit curious of whether I will be able to upgrade from 8.2RC3 or if I should wait until 8.2 is actually released with the setup (I _CAN_ wait a week or two). If you are running 8.2-RC3, you can safely run freebsd-update to go to 8.2-RELEASE. # freebsd-update -r 8.2-RELEASE upgrade You can see for yourself, which releases are supported by freebsd-update: http://update4.freebsd.org/ Since 7.2, every BETA, RC, and RELEASE has been available via freebsd-update (i386 and amd64). I think, the binary diffs are not generated for every combination, but since freebsd-update will fallback to downloading the whole files, even leaving out a few releases should always work. The official announcements usually contain a list of releases supported by freebsd-update, for example 8.2-RC3 was available from 8.0-RELEASE, 8.1-RELEASE, 8.2-BETA1, 8.2-RC1, 8.2-RC2, and "earlier FreeBSD releases (FreeBSD 7.x)". BTW: The 8.2-RELEASE bits are on freebsd-update for almost a day already, the ISOs even a little bit longer, but as always: Wait for the official announcement that is scheduled for today. Cheers, Jan Henrik ___ 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"
Re: Freebsd-update and release candidates
On Tue, Feb 22, 2011 at 11:04 AM, Svein Skogen wrote: > I'm in the process of setting up a small network of FreeBSD > installations. My plan (this time) is to keep them on branches available > to freebsd-update, instead of depending on source being checked out from > CVS. > > However, I'm a wee bit curious of whether I will be able to upgrade from > 8.2RC3 or if I should wait until 8.2 is actually released with the setup > (I _CAN_ wait a week or two). If you are running 8.2-RC3, you can safely run freebsd-update to go to 8.2-RELEASE. # freebsd-update -r 8.2-RELEASE upgrade -- Renato Botelho ___ 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"
Re: Freebsd-update and release candidates
However, I'm a wee bit curious of whether I will be able to upgrade from 8.2RC3 or if I should wait until 8.2 is actually released with the setup (I _CAN_ wait a week or two). Looks like its already been tagged so should be any time now:- /usr/src/UPDATING:- ... 20110221: 8.2-RELEASE. 20101126: New version of minidump format for amd64 architecture was introduced in r215872. To analyze vmcore files produced by kernels at or after this version you will need updated userland, libkvm actually, that is able to handle the new version. Regards Steve This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmas...@multiplay.co.uk. ___ 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"
Freebsd-update and release candidates
I'm in the process of setting up a small network of FreeBSD installations. My plan (this time) is to keep them on branches available to freebsd-update, instead of depending on source being checked out from CVS. However, I'm a wee bit curious of whether I will be able to upgrade from 8.2RC3 or if I should wait until 8.2 is actually released with the setup (I _CAN_ wait a week or two). Any insight would be appreciated. //Svein -- +---+--- /"\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
Re: 3TB disc and block alignment
> Why may it hurt ? How may it hurt ? Which sector is written to by > this 'gpart' command ? > > As far as I understand, GPT writes some stuff at the beginning and > the end of the harddisk. Yup, this is true. > How/why will the newfs overwrite those parts ? Because you are also giving it the whole hard disc to write to, instead of a partition within the hard disc, so you will end up scribbling on what you wrote with the gpart command. -pete. ___ 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"
Re: 3TB disc and block alignment
Hi! > > Basically, I did this: > > > gpart create -s gpt ad7 > > newfs /dev/ad7 > > Wow! Don't do it. It may hurt. ;-) Why may it hurt ? How may it hurt ? Which sector is written to by this 'gpart' command ? As far as I understand, GPT writes some stuff at the beginning and the end of the harddisk. How/why will the newfs overwrite those parts ? > Please, pay attention to gpart(8) (i.e. read the manual > carefully). One should create a specific partition and > only then create a file system upon it. I've read the gpart manual many times 8-) Maybe I'm to thick to get it ? -- p...@opsec.eu+49 171 3101372 9 years to go ! ___ 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"
Re: 8.1 amd64 lockup (maybe zfs or disk related)
On Tue, Feb 22, 2011 at 11:05:00AM +, Bruce Cran wrote: > On Mon, 2011-02-07 at 00:55 -0800, Jeremy Chadwick wrote: > > > # NOTE: Systems with 8GB of RAM or more have prefetch enabled by default. > > vfs.zfs.prefetch_disable="1" > > I think ZFS is enabled with 4 GB or more, not 8 GB: > > "ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is > present; to enable, add "vfs.zfs.prefetch_disable=0" > to /boot/loader.conf." The message ZFS on FreeBSD spits out (shown above) is somewhat inaccurate. I spent the time looking at the code and blogged about the condition over a year ago: http://koitsu.wordpress.com/2009/10/12/testing-out-freebsd-8-0-rc1/ Search for "ZFS NOTICE: system has less than 4GB" on the page above. I still feel the message needs to be re-worded, despite having gone through multiple changes of phrasing already. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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"
Re: 8.1 amd64 lockup (maybe zfs or disk related)
On Mon, 2011-02-07 at 00:55 -0800, Jeremy Chadwick wrote: > # NOTE: Systems with 8GB of RAM or more have prefetch enabled by default. > vfs.zfs.prefetch_disable="1" I think ZFS is enabled with 4 GB or more, not 8 GB: "ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf." -- Bruce Cran ___ 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"
Re: NFS client over udp
--- On Tue, 2/22/11, Rick Macklem wrote: > From: Rick Macklem > Subject: Re: NFS client over udp > To: "Kirill Yelizarov" > Cc: freebsd-stable@freebsd.org > Date: Tuesday, February 22, 2011, 2:10 AM > > --- On Sun, 2/20/11, Rick > Macklem > wrote: > > > > > From: Rick Macklem > > > Subject: Re: NFS client over udp > > > To: "Kirill Yelizarov" > > > Cc: freebsd-stable@freebsd.org > > > Date: Sunday, February 20, 2011, 9:02 PM > > > > --- On Fri, 2/18/11, Kirill > > > Yelizarov > > > > > > On Fri, Feb 18, 2011 at > 05:27:00AM > > > > > > -0800, Kirill Yelizarov wrote: > > > > > > > I have a reproducible memory > leak when > > > using nfs > > > > > > client with an old > > > > > > > nfs server > > > > > > > > and mbufs used > > > > 8193/1722/9915 mbufs in use > (current/cache/total) > > > > 8192/1264/9456/25600 mbuf clusters in use > > > (current/cache/total/max) > > > > 8192/605 mbuf+clusters out of packet > secondary zone in > > > use > > > > (current/cache) > > > > 0/768/768/12800 4k (page size) jumbo > clusters in use > > > > (current/cache/total/max) > > > > 0/0/0/6400 9k jumbo clusters in use > > > (current/cache/total/max) > > > > 0/0/0/3200 16k jumbo clusters in use > > > (current/cache/total/max) > > > > 18432K/6030K/24462K bytes allocated to > network > > > (current/cache/total) > > > > 0/0/0 requests for mbufs denied > > > (mbufs/clusters/mbuf+clusters) > > > > 0/0/0 requests for jumbo clusters denied > (4k/9k/16k) > > > > 0/0/0 sfbufs in use (current/peak/max) > > > > 0 requests for sfbufs denied > > > > 0 requests for sfbufs delayed > > > > 0 requests for I/O initiated by sendfile > > > > 0 calls to protocol drain routines > > > > > > > > Kirill > > > > > > > You could try the attached patch. It fixes the > only places > > > in the > > > client side krpc over udp that seems mights cause > a leak. I > > > have no > > > idea if it will help, since these cases should > rarely, if > > > ever, > > > happen in practice. > > > > > > Please let us know if you have the chance to try > the patch > > > and > > > whether or not it helped. > > > > > > rick > > > > > Rick, i tried your patch. Fortunately it didn't help > me. There are no > > warnings on console and memory is climbing up during > syncs and not > > freed later. I'll try to switch to tcp this evening. > Thanks for help > > > I'll assume that's unfortunately;-) Since the two cases > patched probably > never happen, I'm not surprised. > > The only other thing I can think of that you could try is > switching to > the experimental client. This would identify if the bug is > in the regular > client or somewhere further down in the rpc transport. > > The mount command would look something like: > # mount -t newnfs -o nfsv3,udp : > > I added options NFSCL to my kernel and tried to mount. mount shows everything is ok: 192.168.0.35:/home on /mnt (newnfs) but when i try to cd /mnt i get permission denied my export allow root and everything is done as root. What am i doing wrong? Kirill ___ 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"
Re: 3TB disc and block alignment
Hi! On Tue, 22 Feb 2011 10:23:12 +0100 Kurt Jaeger wrote: > Basically, I did this: > gpart create -s gpt ad7 > newfs /dev/ad7 Wow! Don't do it. It may hurt. ;-) Please, pay attention to gpart(8) (i.e. read the manual carefully). One should create a specific partition and only then create a file system upon it. -- WBR, bsam ___ 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"
Re: Problem with ipfw and libalias on 8.2-PRERELEASE
On 22 February 2011 00:30, Etienne Robillard wrote: > Hi, > > I'm unable to load the ipfw module in 8.2-PRELEASE. i think > this may be due to ABI changes at the kernel level. , > > $ sudo kldload /boot/kernel/ipfw.ko > $ dmesg > ... > KLD ipfw.ko: depends on libalias - not available or version mismatch > linker_load_file: Unsupported file type > > $ uname -a > FreeBSD marina.localdomain 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #1: Wed Feb > 16 03:38:23 EST 2011 > root@:/usr/local/freebsd8/src/sys/amd64/compile/GENERIC.ndebug amd64 > > could there be a more precise explanation? > In recent 8.x you first need to kldload libalias.ko. It was broken in 8 since MFC r200636 (and still broken in head), where ipfw.ko includes ipfw_nat, which depends on libalias. I think either ipfw should un-include ipfw_nat stuff, or pollute self more and take explicit dependency on libalias. -- wbr, pluknet ___ 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"
Re: 3TB disc and block alignment
Hi! > > # glabel status > > Name Status Components > > ufsid/4d62938756e96a72 N/A ad7 > > > If I use gpart, does this somehow imply glabel ? > > I'm not an expert at gpart(8). But my gparted disks have geom labels for > partitions but not for disks: Interesting. > Can you recall exact commands which you used to create desk and > its partitions? Basically, I did this: gpart create -s gpt ad7 newfs /dev/ad7 -- p...@opsec.eu+49 171 3101372 9 years to go ! ___ 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"
Re: Problem with ipfw and libalias on 8.2-PRERELEASE
On 2/21/2011 11:30 PM, Etienne Robillard wrote: KLD ipfw.ko: depends on libalias - not available or version mismatch linker_load_file: Unsupported file type Try a: touch sys/netinet/ipfw/*.c sys/netinet/libalias/*.c env NO_CLEAN=1 make kernel Does this fix the problem? Nikos ___ 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"
Re: 3TB disc and block alignment
Hi! On Mon, 21 Feb 2011 17:55:21 +0100 Kurt Jaeger wrote: > > > > > Feb 17 22:15:44 vserv1 kernel: GEOM: ufsid/4d5d8faa10b63ac1: using > > > > > the primary only -- recovery suggested. > > > > > Boris Samorodov wrote: > > > > It may be the case here if you to used glabel(8) to create a label > > > > for the whole disk. > > > > > I did not use glabel on that disk. > > > > Hm, I may be wrong here but from the log [1] you do have a geom name > > ad7. Can you show an output of the command: > > - > > % glabel status > > - > # glabel status > Name Status Components > ufsid/4d62938756e96a72 N/A ad7 > If I use gpart, does this somehow imply glabel ? I'm not an expert at gpart(8). But my gparted disks have geom labels for partitions but not for disks: - % glabel status Name Status Components ufsid/49dfc483d87d81e7 N/A ada0s2 gptid/3117ed73-3359-11e0-bc0d-001fd091e496 N/A ada1p1 label/swap N/A ada1p2 label/9-i386 N/A ada1p3 gptid/acf7633d-3359-11e0-bc0d-001fd091e496 N/A ada1p4 label/homefs N/A ada1p5 gptid/75213528-28a1-11e0-9c4c-001d60234854 N/A ada2p1 gptid/752e6772-28a1-11e0-9c4c-001d60234854 N/A ada2p2 label/rootfs N/A ada2p3 ufsid/4d3efd0ce038c3e2 N/A ada2p3 gptid/75379a58-28a1-11e0-9c4c-001d60234854 N/A ada2p3 label/varfs N/A ada2p4 ufsid/4d3efd2386112e5e N/A ada2p4 gptid/75447694-28a1-11e0-9c4c-001d60234854 N/A ada2p4 label/usrfs N/A ada2p5 ufsid/4d3efd259218e570 N/A ada2p5 gptid/754e9bec-28a1-11e0-9c4c-001d60234854 N/A ada2p5 label/space N/A ada2p6 ufsid/4d3efd2813378f80 N/A ada2p6 gptid/7557f126-28a1-11e0-9c4c-001d60234854 N/A ada2p6 ufsid/49dfc48396bcec1a N/A ada0s1a ufsid/49dfc496372a8bf7 N/A ada0s1d ufsid/49dfc493241d3645 N/A ada0s1e ufsid/49dfc493e4a185ad N/A ada0s1f - Can you recall exact commands which you used to create desk and its partitions? > You see me confused 8-) NP. Glad to be helpful. ;-) -- WBR, bsam ___ 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"
Re: system crash during make installworld
>> Next I made a copy of the 8.2-RC# install disk and tried to do an upgrade in >> place. It was unable to backup /etc to /var/tmp/etc due to: >> >> ELF interpreter /libexec/ld-elf.so.1 not found >> Abort trap >> >> .. again. This happens pretty much anytime I try to execute a command that >> does not come from /rescue >> >> >> I really rather not do a clean install and lose all my configuration data, >> but it's increasingly looking like that may be my only option. >> >To copy your /etc directory to /var/tmp use: > >/rescue/cp -rp /etc /var/tmp > >Scot That seems to be working. Thanks to all who have helped in sorting out this mess! David ___ 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"
