Re: Fresh 7.0 Install: Fatal Trap 12 panic when put under load
My box crashed again: panic: kmem_malloc(4096): kmem_map too small: 1073741824 total allocated cpuid = 0 Uptime: 33d11h12m58s Dumping 3327 MB (2 chunks) chunk 0: 1MB (151 pages) ... ok chunk 1: 3327MB (851568 pages) <---hung here Still no valid dump. There is 4gig of physical memory in the machine. In /boot/loader.conf, I currently have the following: vm.kmem_size=1G vm.kmem_size_max=1G vm.kmem_size_scale=2 and in my kernel conf file I have: options KVA_PAGES=512 It stayed up for 33 days this time. Is there anything else I can do? Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fresh 7.0 Install: Fatal Trap 12 panic when put under load
On Thu, Sep 11, 2008 at 11:20 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Thu, Sep 11, 2008 at 10:38:36AM +0200, Michael Grant wrote: >> My box crashed again: >> >> panic: kmem_malloc(4096): kmem_map too small: 1073741824 total allocated >> cpuid = 0 >> Uptime: 33d11h12m58s >> Dumping 3327 MB (2 chunks) >> chunk 0: 1MB (151 pages) ... ok >> chunk 1: 3327MB (851568 pages) <---hung here >> >> Still no valid dump. >> >> There is 4gig of physical memory in the machine. >> >> In /boot/loader.conf, I currently have the following: >> >> vm.kmem_size=1G >> vm.kmem_size_max=1G >> vm.kmem_size_scale=2 >> >> and in my kernel conf file I have: >> >> options KVA_PAGES=512 >> >> It stayed up for 33 days this time. Is there anything else I can do? > > First and foremost: are you using ZFS on this machine? If so, there are > many tunables you can apply to try and limit this; I'm willing to bet > it's ARC which is doing it. See below. > > In general, it appears that you need to increase the maximum range of > kmem. The kernel attempted to utilise more than 1GB, and your limit is > 1G. My machines running RELENG_7 on amd64, with only 2GB of RAM > installed, use the following tunables in loader.conf: > > vm.kmem_size="1536M" > vm.kmem_size_max="1536M" > > If ZFS is in use, I recommend these as well: > > vfs.zfs.arc_min="16M" > vfs.zfs.arc_max="64M" > vfs.zfs.prefetch_disable="1" > > Do not increase kmem_size any larger than 1.5GB; the amount of RAM you > have in the machine, with regards to RELENG_7, will not help. This is a > known limitation which has been fixed in HEAD/CURRENT (where the limit > has been increased to 512GB). See the "Kernel" section below; you'll > see the applicable item. > > http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues > > Your only solution may be to run HEAD/CURRENT. I am not running ZFS. My file systems are ufs. This feels like some sort of memory leak in the kernel. Giving it more and more memory just seems to delay the crash. Are you saying the crash is fixed in HEAD/CURRENT? I'm running 6.3 by the way. I have put your changes into my loader.conf, we'll see how long it goes this time. I'm not qute in position to update everything to 7.x at the moment. Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Replication system
On Mon, Nov 3, 2008 at 10:35 PM, Jordi Espasa Clofent <[EMAIL PROTECTED]> wrote: > Hi all, > > I have to build a clustered website with FreeBSD 7.x as SO and Apache 2.x as > httpd. As load-balancing solution I'll use HAProxy (or maybe a OpenBSD > relayd, I'm not sure). > > Because of several technical (and especially non-technical) reasons, I > haven't the possibility to mount a shared storage layer (NFS, SAN...) so I > have to share the local data among the different httpd servers. > > At first approach I've thought in rsync+cron, but > > ¿anyone knows another replication-data solution in the described scenario? > > PD. Please, don't advice to me to using a pure shared-data layer... I know > it will be the optimal structure, but as I've said above, I can't use it > because various reasons. > > -- > Thanks, > Jordi Espasa Clofent GlusterFS http://www.gluster.org seems promising. It is a replication layer that sits on top of FUSE (Filesystem in Userspace http://fuse.sf.net). You can replicate pretty much any type of file system, ufs, zfs, dos...etc. In other words, you don't need to reformat your disk or create some special underlying file system. GlusterFS is in userspace. However.... I have yet to get it working on freebsd. Anyone had any luck with GlusterFS on Freebsd 6.x? Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fresh 7.0 Install: Fatal Trap 12 panic when put under load
On Thu, Sep 11, 2008 at 11:56 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Thu, Sep 11, 2008 at 12:08:47PM +0200, Michael Grant wrote: >> On Thu, Sep 11, 2008 at 11:20 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: >> > On Thu, Sep 11, 2008 at 10:38:36AM +0200, Michael Grant wrote: >> >> My box crashed again: >> >> >> >> panic: kmem_malloc(4096): kmem_map too small: 1073741824 total allocated >> >> cpuid = 0 >> >> Uptime: 33d11h12m58s >> >> Dumping 3327 MB (2 chunks) >> >> chunk 0: 1MB (151 pages) ... ok >> >> chunk 1: 3327MB (851568 pages) <---hung here >> >> >> >> Still no valid dump. >> >> >> >> There is 4gig of physical memory in the machine. >> >> >> >> In /boot/loader.conf, I currently have the following: >> >> >> >> vm.kmem_size=1G >> >> vm.kmem_size_max=1G >> >> vm.kmem_size_scale=2 >> >> >> >> and in my kernel conf file I have: >> >> >> >> options KVA_PAGES=512 >> >> >> >> It stayed up for 33 days this time. Is there anything else I can do? >> > >> > First and foremost: are you using ZFS on this machine? If so, there are >> > many tunables you can apply to try and limit this; I'm willing to bet >> > it's ARC which is doing it. See below. >> > >> > In general, it appears that you need to increase the maximum range of >> > kmem. The kernel attempted to utilise more than 1GB, and your limit is >> > 1G. My machines running RELENG_7 on amd64, with only 2GB of RAM >> > installed, use the following tunables in loader.conf: >> > >> > vm.kmem_size="1536M" >> > vm.kmem_size_max="1536M" >> > >> > If ZFS is in use, I recommend these as well: >> > >> > vfs.zfs.arc_min="16M" >> > vfs.zfs.arc_max="64M" >> > vfs.zfs.prefetch_disable="1" >> > >> > Do not increase kmem_size any larger than 1.5GB; the amount of RAM you >> > have in the machine, with regards to RELENG_7, will not help. This is a >> > known limitation which has been fixed in HEAD/CURRENT (where the limit >> > has been increased to 512GB). See the "Kernel" section below; you'll >> > see the applicable item. >> > >> > http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues >> > >> > Your only solution may be to run HEAD/CURRENT. >> >> I am not running ZFS. My file systems are ufs. >> >> This feels like some sort of memory leak in the kernel. Giving it >> more and more memory just seems to delay the crash. Are you saying >> the crash is fixed in HEAD/CURRENT? > > It's an intentional crash, not "the program tried to access NULL, which > crashed the machine" crash. The kernel wants more memory to accomplish > a certain thing, and it's not available. kris@ can explain this in > better terms than I can. > > First and foremost, it would be good to find out what all you are > running on this machine (process-wise). A process could be tickling > something in the kernel which requires a large amount of memory to be > required. I can imagine something like MySQL would require this. > > Ideally what needs to happen is to debug the kernel or get a full map > of kmem to find out what's using what. I believe vmstat -m or vmstat -z > output might help. > > Obviously since the machine panics, you won't be able to run those > commands after the fact. I would recommend you set up a cronjob that > runs every 1-2 minutes and logs the output of both of those commands > to a file. When the panic happens, restart the system and look at > the logfile to see if you can figure out if anything suddenly starts > taking up a large amount of memory, or if it's a gradual thing > (indicating a memory leak). > > If you can figure out what might be tickling the problem, you can > ultimately figure out if increasing kmem is the right thing to do, or if > there's a greater problem here. > >> I'm running 6.3 by the way. >> >> I have put your changes into my loader.conf, we'll see how long it >> goes this time. I'm not qute in position to update everything to 7.x >> at the moment. > > Our production webservers run RELENG_6 and RELENG_7, and we don't > encounter this kind of problem. I'm not saying what you're experiencing > is indicative of hardware issues or something like that -
Re: Replace Cisco IOS/CBOS with freebsd - possible?
Check out OpenWRT, this is essentially linux (busybox on a linux kernel I believe) that you can load on a router and it runs on more than a handfull of routers. It's not freebsd. Not sure if the Cisco 837 is supported though, but many other routers are. If not supported, just go out and buy a cheap router that is supported and replace your cisco. Michael Grant On Thu, Jan 29, 2009 at 10:50 AM, Chris H wrote: > Greetings, > I'm RP for a fairly large chunk of IP real estate. I carved out > a /27 segment for my home network. Which is currently running over > a cisco 837 GW (adsl/router). I'm not really keen on it (the router/modem). > So I thought to myself that it couldn't be /that/ hard to build a > box with FBSD that could replace it - am I crazy? Wouldn't it > be possible to upload a minimal build of FBSD to the modem, not unlike > one would tftp a new version of cisco's IOS, or CBOS? I searched > the projects area to see if anyone had tried it. But the only thing > that came anywhere near was netperf. But the only similarity is that it > is network related. Anyway, this seems quite feasable as far as I can > tell. So I thought I'd ask in hopes someone might enlighten me further. > Maybe someones already tried it? > > Thank you for all your time and consideration in this matter. > > --Chris > > > ___ > 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-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
swap_pager: indefinite wait buffer
My server just literally was brought to it's knees with this message spewing on the console: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1203133, size: 4096 (blkno and size were varying) Some searching says that this is or was a bug. Has this been fixed yet? If so, what should I upgrade to? I'm currently running 6.3 Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: swap_pager: indefinite wait buffer
On Wed, Mar 5, 2008 at 11:08 AM, Ruben van Staveren <[EMAIL PROTECTED]> wrote: > On 5 Mar 2008, at 10:06, Michael Grant wrote: > > > My server just literally was brought to it's knees with this message > > spewing on the console: > > > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1203133, size: > > 4096 > > > > (blkno and size were varying) > > > > Some searching says that this is or was a bug. Has this been fixed > > yet? If so, what should I upgrade to? I'm currently running 6.3 > > You may consider partition backed swap instead of file backed swap if > that is the case. Hmm, I can't easily do that, I didn't leave any empty partitions around as I never considered swapping to a file to be a so bad. Is swapping to a file so bad under normal conditions? Does this mean that this bug is still not fixed in 7.0? Is there any way to do anything akin to Partition Magic on ufs to shrink the fs? (not sure if it's ufs1 or ufs2, mount reports it as 'ufs'). Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading to 7.0 - stupid requirements
My server is live and serving customers. I can't afford to take the box down for a whole day while I upgrade ports. Is there any intelligent way to do this? For example, could I do everything on a second disk while running the live system on the first disk? For example using a chroot so it thinks it's For example, might this work? 1) upgrade system in the canonical way: # make buildworld # make buildkernel # make installkernel # reboot # mergemaster -p # make installworld # mergemaster # reboot 2) make sure misc/compat6x is installed 3) on a second disk or in a directory somewhere like /new a) nullfs mount read-only all the things one needs inside a chroot to work except /usr/local b) create a writable /usr/local, /usr/X11R6, /compat/linux and /var/db in the chroot 4) then for each package installed, install it within the chroot 5) when all that's done, drop into single-user mode and move /usr/local, /usr/X11R6, /compat/linux, and /var/db/pkg to the real system (saving the old ones) 6) reboot Warning, I have never tried this. -Mike On Wed, Mar 19, 2008 at 11:47 AM, Oliver Fromme <[EMAIL PROTECTED]> wrote: > Hello Marko, > > I'm very sorry that you have trouble updating your FreeBSD > installation, but there are very good technical reasons to > update your packages, as others have already explained in > detail (i.e. library conflicts). > > When I updated my home workstation from FreeBSD 6 to 7, > I used the opportunity to clean up my installed packages, > which was long overdue anyway. > > First I saved the output from "pkg_info" in a file. Then > I edited it and removed everything that I don't need. > There was lots of superfluous crap in it, like ports that > I installed once out of curiosity but never continued to > use them, and ports that were installed as a dependency > once but aren't required anymore because the dependent > software is long gone. > > Then I did "pkg_delete \*", checked for left-overs in > /usr/local because not everything was removed cleanly, > and then installed the ports from my text file again. > I chose to compile from ports instead of installing > precompiled packages because the machine is fairly fast > (if you have a slow machine, installing packages will > be much faster, of course). > > It certainly went a lot quicker than if I had blindly > updated all ports without cleaning up. And now all of > my installed packages are guaranteed to be fresh and > up to date, and I only have the stuff on my harddisk > that I really need. > > Really, such situations where you should update all of > your packages is the best opportunity to clean up the > mess that has accumulated on your disk in a long time. > I recommend that everyone considers doing that, too, > instead of blindly running portupgrade. Of course, > the latter would work, too, but it takes longer and > will rather add to the mess instead of cleaning it. ;-) > > Best regards >Oliver > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. > Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: > secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- > chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart > > FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd > > Python is executable pseudocode. Perl is executable line noise. > > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fresh 7.0 Install: Fatal Trap 12 panic when put under load
On Wed, Jul 16, 2008 at 10:38 AM, John Sullivan <[EMAIL PROTECTED]> wrote: > >> Could be memory, but I'd also suggest looking at >> temperatures. I've had overheating systems produce lots of >> such errors. > > Temperature is fine - it never get's that hot here in the UK ;-) Seriously, > I put my hand in the box, touched a few heat sync's, it > is not running hot enough to cause a problem. The BIOS reports that all is > well with the temperature inside the box of just over 30 > degrees C. > > John > This looks like the same panic I reported yesterday but I'm running 6.3 patch 2. I have seen these crashes on my box since 6.3 pre-release, randomly, but under load. My box is based on a SuperMicro motherboard running Intel Xeon processors. The only commonality is that we're both using Sata drives. John, a question, how is swap set up on your system? I was swapping to a file (a memory disk device /dev/md0). I was doing this because for some reason lost in ancient history, this machine was not set up with a real swap partition. Hence, no crash dump. Last night I repartitioned a second disk, set up a real swap partition and now I'm currently waiting for this to happen again so I can get a crash dump. Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fresh 7.0 Install: Fatal Trap 12 panic when put under load
I have been having what seems like similar panics. I too cannot manage to get a crash dump, neither classic style nor minidump. Nor can I get it to work with DDB, there seems to be a problem with DDB and my Geom mirror. Kris recommended I up kmem_size which I have done (twice now) and since the last time I upped it, the machine has not crashed again (yet?). For the moment, I'm hoping things are stable. In /boot/loader.conf, I currently have the following: vm.kmem_size=1G vm.kmem_size_max=1G vm.kmem_size_scale=2 and in my kernel conf file I have: options KVA_PAGES=512 Here's what top says currently: last pid: 57367; load averages: 0.56, 0.54, 0.61 up 2+10:16:57 15:50:55 407 processes: 6 running, 378 sleeping, 2 zombie, 21 waiting CPU states: 0.1% user, 0.0% nice, 2.3% system, 0.7% interrupt, 97.0% idle Mem: 1309M Active, 1291M Inact, 497M Wired, 155M Cache, 199M Buf, 7408K Free Swap: 9541M Total, 1628K Used, 9540M Free Is this a heavily loaded machine? It's using a lot of memory, but it's mostly idle. I have 2 sticks of double-sided memory (4gig total) in the box. The SuperMicro documentation recommends using single sided sticks for 6 or more sticks. I feel for you John, I've lost many nights sleep in the last couple weeks trying to understand why this production box was crashing. I was really surprised to see this start happening, normally my freebsd boxes have uptimes in terms of years, not hours. Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Adding multiipul virtual domains?
On Tue, Jun 23, 2009 at 17:04, eculp wrote: > Quoting ALLnetgroup : > >> The server has 1 domain name already setup along with: >> >> sendmail >> Webmin >> Apache Web Server >> MySQL >> Apache Tomcat >> Squid Proxy >> SOCKS5 >> PERL >> Mod PERL >> PHP >> OpenSSH >> phpBB >> RoundCube WebMail >> >> When I add a new virtual host I would like the host to have it's own >> directory, website and the services above. There is nothing that I know of that will automatically "add a new virtual domain" to a machine in all of these systems. I have my own home brew perl scripts which do such things but they are not usable outside my own environment. Many other people I have talked to have done the same thing or just configured each of these individually. If you are not technically savvy enough to write your own configuration management system or to modify the configuration files individually, you might consider instead of having your own machine to use a web hosting company which automatically installs and configures this stuff for you via a control panel. Incidentally this is not the first time I have seen a need for some larger "meta" confutation system for unix/linux in general. It's absolutely true that adding a domain to a system is often a multi-step process and it need not be. Like adding a user in the old days when you first edited the passwd file, the group file, made the home directory and copied over some dot files there, now it's all automated in the adduser command. A user might have several domains, mail, one or more web sites, etc. All of this gets configured into lots of different files. Then think what happens when you get rid of a user. There really aught to be some easier way which is why I ended up writing my own scripts. Michael Grant ___ 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"
bios disk numbers and device names
Is there any way to statically assign a device name to a specific disk so that if the BIOS renumbers the disks (for example if I move around a controller) so that the devices always come up with the same name? Michael Grant ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bios disk numbers and device names
On Mon, Nov 29, 2004 at 09:33:25PM +1030, Daniel O'Connor wrote: > On Mon, 29 Nov 2004 20:40, Michael Grant wrote: > > Is there any way to statically assign a device name to a specific disk > > so that if the BIOS renumbers the disks (for example if I move around > > a controller) so that the devices always come up with the same name? > > The BIOS naming means nothing to freebsd (in general). > > I don't think there's much you can do - device names are based on the order > of > probing so if you change which slot on the controller it's connected to it > will change device name. > > What sort of device in particular? Specifically, ata and scsi. This is a big problem for me. Once I lost a controller and it was a nightmare trying to get the machine to boot after moving the disks to the other controller. Another time I added a disk and again it was a nightmare. Has anyone thought about this problem? Is there some spare space in the label that could be used for a device name that, if set, could be used in place of (or an alias for) a name like da0? Michael Grant ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bios disk numbers and device names
Thanks, that seems like it will work perfectly. Do you know if I can boot a root device on say /dev/ufs/root? tunefs -L root /dev/da0a then in my fstab: /dev/ufs/root / ufs rw 1 1 Also, what is the difference between dong 'glabel lable -v root' and 'tunefs -L root'? It appears from the man page that one creates a /dev/label/root and the other creates a /dev/ufs/root. Where can I learn more about /dev/label and /dev/ufs? Thanks again. Michael Grant On Mon, Nov 29, 2004 at 01:39:58PM +0100, Andrea Campi wrote: > On Mon, Nov 29, 2004 at 07:21:00AM -0500, Michael Grant wrote: > > Has anyone thought about this problem? Is there some spare space in > > the label that could be used for a device name that, if set, could > > be used in place of (or an alias for) a name like da0? > > GEOM_LABEL is what you're looking for. Check the glabel(8) man > page. In a nutshell, you'd do this: > > tunefs -L log /dev/ad1s1a > tunefs -L db /dev/da4s1a > tunefs -L www /dev/da4s1a > ... > > mount /dev/ufs/log /mnt/log > mount /dev/ufs/db /mnt/db > mount /dev/ufs/www /mnt/www > > (you get the idea). Obviously you can move use the /dev/ufs/* > devices in fstab as well. > > If later on you move the filesystems to a different device while > retaining the label (which means no tar, you have to use dd or > dump/restore), everything works. > > Hope it helps. Bye, > Andrea > > -- > Give a man a fish and you feed him for a day; > teach him to use the Net and he won't bother you for weeks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: is it possible to mount a vinum-fs on 2 hosts?
I would love to see a cluster capable filesystem for freebsd. I do not know if this will help your situation but I have seen people mount the file system read/write on Host A and then mount the file system from Host A via NFS on Host B. This allows B to write to the file system using A. Michael Grant On Sun, Dec 12, 2004 at 09:41:28PM -0800, Doug White wrote: > On Thu, 9 Dec 2004, Michael Schuh wrote: > > > I hav Host A andHost B both are connected to an SAN > > through an QLA2200 Fibre-Channel (man isp). > > On the SAN are 14 Disks da0-da13 these Disks are configured > > w/ vinum to an RAID 10 Filesystem. > > > > Now i have the Problem i would make Host A to an PDC and > > HOST B to an BDC. > > To be redundant in an fail of the PDC (Host A) i would have access to the > > SAN > > from BDC (Host B). > > > > Now i Know the Problem of an already mounted Filesystem. > > I would mount the Filesystem on both Hosts, may i cannot update > > the Filesystemdescriptors from Host A on Host B. > > FreeBSD does not currently ship with a cluster-capable filesystem, so this > configuration is not supported out of the box. Unless someone offers a > cluster-capable filesystem as an addon product ... and I guess that's what > your fishing for :) > > -- > Doug White| FreeBSD: The Power to Serve > [EMAIL PROTECTED] | www.FreeBSD.org > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Canonical 4.x to 6.x upgrade docs?
Has anyone succeeded in doing a 4.x -> 6.x upgrade from source without upgrading first to 5.x as an intermediate step? Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Adaptec AIC9410
Can anyone tell me if/when the Adaptec AIC9410 SAS/SATA controller will be supported? Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Adaptec AIC9410
I just bought a Supermicro X6DH3-G2 with some Maxtor 500gig SATA drives. The box sees the SATA drives in the bios but of course not in Freebsd. Do you think I can use the MPT driver from 7-current and use in 6-stable with these SATA drives? Michael On 3/15/06, Scott Long <[EMAIL PROTECTED]> wrote: > Michael Grant wrote: > > > Can anyone tell me if/when the Adaptec AIC9410 SAS/SATA controller > > will be supported? > > > > Michael Grant > > It's on my TODO list, but realistically I won't even be able to think > about starting it until this summer at the earliest. The MPT driver > has prototype support for SAS (in 7-current for now), so that might > be a better alternative. > > Scott > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mdconfig
I'm mounting a snapshot using mdconfig, then mount like this: mdconfig -a -t vnode -f /home/.snap/4 -u 0 mount /dev/md0 /snapshot/home mount (with no args) shows this: /dev/md0 on /snapshot/home (ufs, local, read-only) # mdconfig -l -u md0 md0 vnode 23503425 KBytes How can I see (to verify) what file md0 is based on? Perhaps this should be part of the mdconfig -l output? Furthermore, could we have that info when we run mount (with no args) and df? Or might that break something that depends on their output? Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
disappearing snapshots
I've been playing with snapshots (mksnap_ffs) recently. I've got a script which does a daily snapshot and keeps 7 days of history. Last night, the machine crashed and when it came back up, all the snapshots referred to the current view of the disk, i.e. I lost the 7-day history. I'm running 5.3-release. Has anyone seen this? Snapshots should persist beyond reboots, shouldn't they? (Yes, I am doing the mdconfig and remounting the snap.) Michael Grant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
problem booting after install of 5.1
I just did a fresh install of 5.1-release. I'm using the freebsd bootloader to choose between 2 disks. Freebsd is on the second (da1) disk and windows on the first (da0). The first time I booted the machine, I got this: F1 FreeBSD F5 Drive 1 Default: F1 If I pressed F1, it just beeped. Pressing F5 gave me an error in french and now when I reboot again, the default is F5 and every key beeps, nothing seems to be able to get it to give me the error again and nothing will advance it beyond this menu. The error being in french is probably because I have the french version of xp loaded on the other disk, though I'm not 100% sure if the error came from windows or the bootloader (which should be in english I thought). Michael Grant ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
