Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64
On Sun, 31 Jan 2010 17:56:39 +0100 Torfinn Ingolfsen wrote: > On Sun, 31 Jan 2010 14:42:17 +0100 > Torfinn Ingolfsen wrote: > > > Hi, > > > > One of my machines had a panic or something. > > The machine was pingable, but I couldn't ssh into it, and there was no > > response on the console. > > > > And it did it again, only a few hours later. I'll try to update to latest > -stable, and see if that helps. > Same messgae as last time, unfortunately I didn't record tge details (tid and > pid). Oh well. Well, it was stable for many days, but today it rebooted on its ownb again. After the fact, I see this in /var/log/messages: Feb 7 11:50:16 kg-f2 ntpd[906]: time reset +2.376096 s Feb 7 12:02:21 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 007f Feb 7 12:02:21 kg-f2 kernel: ata6: hardware reset timeout Feb 7 12:05:43 kg-f2 syslogd: kernel boot file is /boot/kernel/kernel So there is probably some problem with a cable or disk. On the plus side, it did reboot and came upa agin without any issues. -- Regards, Torfinn Ingolfsen ___ 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"
one more load-cycle-count problem
Hi all, After being disturbed by the firmware issues of the wd drives causing exceeding load cycles (see thread "immense delayed write to file system (ZFS and UFS2), performance issues" in January), I have found some more problematic drives in the following setup: 4 x 2.5" WDC WD4000BEVT-00ZAT0 in RAIDZ1 configuration attached to a Supermicro SAS controller: m...@pci0:2:0:0:class=0x01 card=0xa38015d9 chip=0x00581000 rev=0x08 hdr=0x00 vendor = 'LSI Logic (Was: Symbios Logic, NCR)' device = 'SAS 3000 series, 8-port with 1068E -StorPort' class = mass storage subclass = SCSI luna# camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 2 lun 0 (pass2,da2) at scbus0 target 3 lun 0 (pass3,da3) The disks appear to load/unload every 10s or so if I do not artificially keep them busy. Does anyone here have a suggestion how to make this interval longer or even turn off the unload feature completely? I tried luna# camcontrol idle da0 -t 600 (pass0:mpt0:0:0:0): CMD: IDLE: e3 00 00 00 00 40 00 00 00 00 78 00 (pass0:mpt0:0:0:0): CAM Status: CCB request was invalid luna# camcontrol standby da0 -t 600 (pass0:mpt0:0:0:0): CMD: STANDBY: e2 00 00 00 00 40 00 00 00 00 78 00 (pass0:mpt0:0:0:0): CAM Status: CCB request was invalid >From /usr/share/misc/scsi_modes I gather that page 26 should contain power control features, but no avail: luna# camcontrol modepage da0 -m 26 camcontrol: error sending mode sense command Any further ideas how to get rid of this "feature"? cu Gerrit ___ 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: Zombie NFS writing from FreeBSD clients to FreeBSD 8.0 server with ZFS
--- On Wed, 2/3/10, Rick Macklem wrote: > From: Rick Macklem > Subject: Re: Zombie NFS writing from FreeBSD clients to FreeBSD 8.0 server > with ZFS > To: "alan bryan" > Date: Wednesday, February 3, 2010, 8:02 AM > > > On Tue, 2 Feb 2010, alan bryan wrote: > > > I've tried different network driver igb->em, > UDP->TCP for NFS, enabling NFS locking on the > server/clients (lockd, statd). > > > I'm out of ideas so hoping this tcpdump sheds light on > how it's getting stuck in this loop. > > You could try the experimental server, just to see if that > has any effect. > Either set nfsv4_server_enable="YES" or add "-e" to both > nfs_server_flags > and mountd_flags. > > Note that the server will handle NFSv3, so you don't need > to use NFSv4 > mounts. > > rick > Thanks - I might give that a try. This was only initially happening on our production stack which made it difficult to try things to troubleshoot. I've since been able to get it to happen on our dev stack too. Basically - I have about 70 mounts from the clients. 70 or so separate ZFS filesystems each exported via sharenfs. This appears to work well at first. After some traffic and some time (less than a day) the zombie writes start occuring. So, on dev we enabled dtrace (not at all familiar with it unfortunately) and tried to get this to happen. When it did happen we could see some patterns to the calls which matches up to the repeating conversations witnessed in the tcpdumps. zpool iostat when this is occuring is showing nothing being written to the disks. So, it appears that the client is requesting a write, NFS takes the request, asks ZFS which is replying with some error (from it's cache?) and then back to the client again. So, I'm starting to lean to this being more of a ZFS issue than an NFS one but I'm still not sure. We've read the recommendations about disabling the ZIL for ZFS/NFS and that sounds a bit scary. We've bought some Intel X25-E SSDs to mirror for a log device to add to the pool instead to see if that makes any sort of difference. (the thinking here is that this is now appearing like it might be a ZFS issue and that the speed of the SSDs plus the different code path in dealing with a dedicated log device might help us avoid the issue). So, if the SSDs don't change the behavior I may give the experimental NFS server a try to see if it helps. Thanks, Alan ___ 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: Inmutable bit in some binaries
On 2010-Feb-06 12:11:08 +0100, Pascal Stumpf wrote: >just another idea: You may want to take a look at integrity checking systems >as an alternative, i.e. tripwire. Note that mtree(8) supports the integrity checking functionality of tripwire and is in the base system. (It doesn't have all the bells and whistles of tripwire and so isn't suitable for all cases). If you do go for an integrity checking system, remember to ensure that everything that your integrity checking system relies on (ie executable, database, shared libraries) is immutable - as well as the shell/cron that runs it and however the results are reported. -- Peter Jeremy pgpNTKkUgGATK.pgp Description: PGP signature
Re: Kerberized NFSv3 incorrect behavior
On Sat, 6 Feb 2010, George Mamalakis wrote: thank you for all your answers. I am planning on setting up the computer labs of my department using kerberized nfsv3 (since v4 seems to be "more" experimental) with a FreeBSD nfs server and Linux nfs clients. I was wondering "how stable" such an implementation would be; meaning that I wouldn't want to end up with an unstsable setup when receiving requests from 50-60 simultaneous clients, because that would be my everyday scenario. I believe that the above should be stable, but your mileage may vary, as they say. The main issue will be what your TGT lifetime will be, since client access to the server will normally stop when the TGT expires. Some systems (Mac OS X) will automagically renew the TGT before it expires, if your KDC allows that. I don't think most/all Linux systems do this by default, but there are some utilities out there (try a search for krenew) that will do so. Basically, I think you'll want to avoid TGTs expiring before the user logs out. You also need a unique uid<->user principal mapping for all users logging in. You definitely want to do some testing with whatever Linux system you are using for the client. Good luck with it, rick ps: Choosing nfsv3 vs nfsv4 is basically independent of using RPCSEC_GSS except for the host based initiator credential needed by some clients (Linux and Solaris10 are among those) for NFSv4. ___ 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"
hardware for home use large storage
Hi, I'm looking at creating a large home use storage machine. Budget is a concern, but size and reliability are also a priority. Noise is also a concern, since this will be at home, in the basement. That, and cost, pretty much rules out a commercial case, such as a 3U case. It would be nice, but it greatly inflates the budget. This pretty much restricts me to a tower case. The primary use of this machine will be a backup server[1]. It will do other secondary use will include minor tasks such as samba, CIFS, cvsup, etc. I'm thinking of 8x1TB (or larger) SATA drives. I've found a case[2] with hot-swap bays[3], that seems interesting. I haven't looked at power supplies, but given that number of drives, I expect something beefy with a decent reputation is called for. Whether I use hardware or software RAID is undecided. I I think I am leaning towards software RAID, probably ZFS under FreeBSD 8.x but I'm open to hardware RAID but I think the cost won't justify it given ZFS. Given that, what motherboard and RAM configuration would you recommend to work with FreeBSD [and probably ZFS]. The lists seems to indicate that more RAM is better with ZFS. Thanks. [1] - FYI running Bacula, but that's out of scope for this question [2] - http://www.newegg.com/Product/Product.aspx?Item=N82E16811192058 [3] - nice to have, especially for a failure. ___ 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: hardware for home use large storage
On Mon, 8 Feb 2010, Dan Langille wrote: > Given that, what motherboard and RAM configuration would you > recommend to work with FreeBSD [and probably ZFS]. The lists seems > to indicate that more RAM is better with ZFS. I have something similar (5x1Tb) - I have a Gigabyte GA-MA785GM-US2H with an Athlon X2 and 4Gb of RAM (only half filled - 2x2Gb) The board has 5 SATA ports + 1 eSATA (I looped that back into the case to connect to the DVD drive :). I boot it off a 4Gb CF card in an IDE adapter. I think you could boot off ZFS but it seemed a bit unreliable when I installed it so I opted for a more straightforward method. The CPU fan is fairly quiet (although a 3rd party one would probably be quieter) and the rest of the motherboard is fanless. The onboard video works great with radeonhd (it's a workstation for someone as well as a file server). Note that it doesn't support ECC, I don't know if that is a problem. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
