How to debug fatal trap? running on vinum
Had FreeBSD5.1 on a box that had a physical hard-drive failure last week. So, this time setup the box using mirrored 200GB drives using vinum sub-disks. Setup multiple vinum partitions to help limit any file system corruption. One of those partitions was /dev/vinum/ports which points to /usr/ports. Once the machine was setup with a minimal install, then did a restore from the image made before the original hdd failure. I've never done that before, so there is a possibility that I might have restored a file that I should not have. Got ports updated using cvsup. Then did a make reinstall of /usr/ports/x11/kde3. The last thing I saw before fatal trap reboot was the following: --- === Extracting for libxml2-2.5.8_1 Checksum OK for gnome/libxml2-2.5.8.tar.bz2. Fatal trap 12: page fault while in kernel mode fault virtual address= 0x14 fault code = supervisor write, page not present instruction pointer = 0x8:0xc02d15d9 stack pointer= 0x10:0xcdb35aa8 frame pointer= 0x10:0xcdb35adc code segment = base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 39 (buffdaemon) trap number = 12 panic: page fault syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue Terminate ACPI Automatic reboot in 15 seconds - --- Any tips on how to debug this or if there is an article that discusses how to do this I would be very grateful for any help. The only way I know how to fix is to rebuild everything - including setting up the vinum volume up again. Takes too long, hoping for a better solution. Clearly a newbie. Thanks, Richard ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Vinum on Root
I went back to the original root install method as per the book, and I got vinum working. Now, needed to change the size of the var volume, since during install I followed the book example and had var take up the rest of the disk, in my case all 187Gigs of it :). Was under the impression that it would be easy to resize or at least remove and create a new smaller var once the base is working. So, backed up the /var directory. Started the vinum prompt and used rm to remove the var subdisk, then remove the var plex and finally was able to remove the var volume. Now ran create vinum_var.conf - in this case the file was simply: volume var plex org concat sd len 1g drive rootdev So, did not use the offset, since vinum is now working and should know where the next 1g should come from. Is this a bad assumption? Well, the vinum create worked fine. Then copied the backed up /var contents to the new vinum volume. Did a reboot, and reboot failed. System requesting to run fsck. So, in single user mode did this and got the following error: ** /dev/vinum/var (NO WRITE) CANNOT READ BLK: 381244736 CONTINUE? Yes THE FOLLOWING DISK SECTORS COULD NOT BE READ: 381244736, 381244737, 381244738, 381244739, /dev/vinum/var: CANNOT FIGURE OUT FILE SYSTEM PARTITION So, what should I have done and is there a way to back out of this? By the way, it a great book, I'm just a little thick when it comes to vinum new unix. So, know I'm trying to do a lot right out of the gate - so really appreciate all the help I've been getting from everybody! Thanks again, Richard I. 1. setup unix partitions for swap, /, /usr, and /var 2. install FreeBSD5.1 3. go through the bsdlabel -e 3.1 modify the swap with the 281 offset 3.2 add vinum partition h: with the same size as c:, but with a 16 offset 4. create a vinum config file -- 4.1 map each sub-disk to the exact size and offset as the unix partitions II.1. setup unix partitions for swap and / 2. install FreeBSD5.1 3. go through the bsdlabel -e 3.1 modify the swap with the 281 offset 3.2 add vinum partition h: with the same size as c:, but with a 16 offset 4. create a vinum config file -- 4.1 create sub-disks using simply the size you want with no offset So, if I use Method I, as you specified in the book, can I then move those particular partitions (/, /usr, /var) around without worrying about the original unix partition layout (offsets etc)? So, the original /, /usr, /var sizes and offsets won't limit the location of the /dev/vinum/root, /dev/vinum/usr, /dev/vinum/var? They will for root, because you boot from the partition, not the volume. Also, you should understand that moving partitions means moving data. For the mirroring case, should the swap partitions be mirrored too? That depends on whether you want to still have a swap partition if a drive fails :-) Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
imake won't install-4.3.0
Using sysinstall, was going to install emacs and kde. Install failed on installing imake. The error I got Was Add of package imake-4.3.0 aborted, error code 1 - Please check the debug screen for more info. , then got Loading of dependent package imake-4.3.0 failed. Where is this debug screen I'm supposed to look at? Tried doing a portinstall imake. This failed as well. This was after I did: 1) cvsup -g -L 2 cvsup.conf, 2) portsdb -Uu, 3) pkgdb -F, 4) portupgrade -ra Don't know how to fix this. Overview: - Installed FreeBSD 5.1 Release. - Modified the install unix partitions to support vinum worked after a lot of help from people on this list. - Did as much restore of the previous image the machine had before it crashed. Should have had vinum back then! - Also, added some RCS version control for the config files under /etc, /usr/local/etc, and /root How's the best way to debug this. What files should I be looking at? Thanks in advance for any tips, Richard ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: information
This is where I got the latest ISO: ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/ISO-IMAGES/5.1 -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of gerardo diaz Sent: Thursday, July 31, 2003 9:25 PM To: [EMAIL PROTECTED] Subject: information where i can download free FreeBSD, thanks GERARDO DIAZ PERU ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Vinum on Root
Sorry, my bad - needed to do newfs. Once I did this the fsck worked perfectly. Thanks again for all the help. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Mirroring Vinum Volumes - importance of subdisk sequence on mirrordevice
Question: Is it important that the sequence plexes/sub-disks get created in for the primary drive and the mirrored drive be the same? Any performance penalty? I'm guessing that a different sub-disk creation order will put the sub-disks in different places on a disk. Background - if needed: Have 10 vinum volumes being mapped by 10 plexes to the root drive. To get mirroring, I created plexes/sub-disks for swap, root, and usr using the specific offsets for each on the 2nd hdd device and map them back to their specific volumes they should be mirroring. When I start creating the other plexes/sub-disks on the 2nd hdd and map them back to the volume already setup, I won't be using specific offsets. Thanks, Richard ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Mirroring Vinum Volumes - importance of subdisk sequence onmirrordevice
It seems dumpconfig provides absolute settings of the subdisks. Might as well use those offsets just in case it matters. -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Richard Johannesson Sent: Wednesday, July 30, 2003 1:52 PM To: [EMAIL PROTECTED] Subject: Mirroring Vinum Volumes - importance of subdisk sequence on mirrordevice Question: Is it important that the sequence plexes/sub-disks get created in for the primary drive and the mirrored drive be the same? Any performance penalty? I'm guessing that a different sub-disk creation order will put the sub- disks in different places on a disk. Background - if needed: Have 10 vinum volumes being mapped by 10 plexes to the root drive. To get mirroring, I created plexes/sub-disks for swap, root, and usr using the specific offsets for each on the 2nd hdd device and map them back to their specific volumes they should be mirroring. When I start creating the other plexes/sub-disks on the 2nd hdd and map them back to the volume already setup, I won't be using specific offsets. Thanks, Richard ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Vinum Sub-disk Directory Structure Mapping
Using the unlimited number of sub-disk that can be created using vinum, what's a good way to separate the directory file structure to help limit file system corruption? Or, what's the happy medium between limiting fs corruption and complexity? Here's my guess of which part of directory structure should be on its own sub-disks/filesystem: / Probably /root Overkill? /usrProbably /usr/local /varProbably /var/backups? /tmpProbably - or should be on same as var? /home Maybe - or should be under /usr? /stand ? /boot ? Any feedback is very much appreciated. If there is document that discusses this basic topic while taking vinum into account, please let me know so I can bugger off. :) Thanks again, Richard ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Vinum on Root
Is it possible to create vinum on a root drive without using the offsets in the vinum configuration file? What I trying to get to is that there seems to be two styles of getting vinum setup on a root drive: I. 1. setup unix partitions for swap, /, /usr, and /var 2. install FreeBSD5.1 3. go through the bsdlabel -e 3.1 modify the swap with the 281 offset 3.2 add vinum partition h: with the same size as c:, but with a 16 offset 4. create a vinum config file --4.1 map each sub-disk to the exact size and offset as the unix partitions II.1. setup unix partitions for swap and / 2. install FreeBSD5.1 3. go through the bsdlabel -e 3.1 modify the swap with the 281 offset 3.2 add vinum partition h: with the same size as c:, but with a 16 offset 4. create a vinum config file --4.1 create sub-disks using simply the size you want with no offset Method I. comes from the Complete FreeBSD book. I actually got this to work, but was wondering about the inflexibility of not being able to change the partition sizes very easily. Method II. Can't get this to work yet, but if it can work then should be superior given the flexibility that is gained. So, can Method II work on a root drive? If Method II works, why would you then ever want to implement Method I? Thanks again, Richard ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Vinum on Root
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Greg 'groggy' Lehey Sent: Tuesday, July 29, 2003 6:25 PM To: Richard Johannesson Cc: [EMAIL PROTECTED] Subject: Re: Vinum on Root On Tuesday, 29 July 2003 at 18:00:25 -0700, Richard Johannesson wrote: Is it possible to create vinum on a root drive without using the offsets in the vinum configuration file? You need a configuration file to set up Vinum. If you mean Is it possible to create vinum on a root drive without specifying offsets in the vinum configuration file?, the answer is yes. Sorry that's what I meant. Ok, that's good to hear. What I trying to get to is that there seems to be two styles of getting vinum setup on a root drive: I. 1. setup unix partitions for swap, /, /usr, and /var 2. install FreeBSD5.1 It doesn't have to be 5.1. Ok, good to know. 3. go through the bsdlabel -e 3.1 modify the swap with the 281 offset 3.2 add vinum partition h: with the same size as c:, but with a 16 offset 4. create a vinum config file --4.1 map each sub-disk to the exact size and offset as the unix partitions II.1. setup unix partitions for swap and / 2. install FreeBSD5.1 3. go through the bsdlabel -e 3.1 modify the swap with the 281 offset 3.2 add vinum partition h: with the same size as c:, but with a 16 offset 4. create a vinum config file --4.1 create sub-disks using simply the size you want with no offset Method I. comes from the Complete FreeBSD book. I actually got this to work, but was wondering about the inflexibility of not being able to change the partition sizes very easily. Once you have Vinum up and running, you can add and remove plexes and move things around like that. So, if I use Method I, as you specified in the book, can I then move those particular partitions (/, /usr, /var) around without worrying about the original unix partition layout (offsets etc)? So, the original /, /usr, /var sizes and offsets won't limit the location of the /dev/vinum/root, /dev/vinum/usr, /dev/vinum/var? Method II. Can't get this to work yet, but if it can work then should be superior given the flexibility that is gained. That'll work, but then you need to populate the volumes. So, can Method II work on a root drive? Sure. If Method II works, why would you then ever want to implement Method I? It's easier. You don't have to find a way to put things in your new volumes. Ok, Method I is the best way to bootstrap the whole process, and once you have a base setup running on vinum you still have the flexibility of Method II anyway. If that's right, then Method I is definitely the way to go. Greg For the mirroring case, should the swap partitions be mirrored too? Was under the impression that swap might be handled by a completely separate process and that there was no need for vinum to have to handle any swap stuff. Thanks again, Richard -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html See complete headers for address and phone numbers ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD5.1 Vinum Mirror root
Machine will run one copy of FreeBSD5.1 and has three hard drives: 2 x 200GB and 1 x 100GB drives. I was planning to use the 100GB for backup to store dump images of this machine. The 200GB drives are mirrored root vinum volumes - however that is accomplished. The purposed of the machine: - Backup server + Stores dump images of 5 web servers - Web server configuration website version control + Should store the configuration files of each web server + Web pages are published to this server * Each webserver should sync its config files and webpages with this configuration server - not sure which method is the best: rsync, cvsup, other? - Intranet webserver running apache Using mod_python + perl cgi Intranet Wiki Server to capture notes (twiki looks the best so far) - Keeps FreeBSD 5.1 up-to-date using cvsup nightly. - Build server Will keep kernel + apps up-to-date as needed Plan to have web server just run the make install via NFS from this build server I know I'm asking too much of this machine, but that's why something like vinum should be on it. Clearly, reliability is paramount. Is there ever an advantage of having two slices for a drive when running just one copy of FreeBSD on there? So, let's say split the 200GB into two slices. First will have the standard partitions /, /var, /tmp, swap, /usr. Then have /data on 2nd slice. What's the disadvantage of doing this? How will this affect vinum - better or worse? I understand that having more unix partitions might help limit data corruption if the machine crashes. So was planning to split things up into partitions as the following: / - 256MB, swap - 512MB, /var - 1GB, /tmp - 256MB, /usr - 198GB (rest). Should these partitions be done under ufs2 and then put vinum on each, or should I just have one giant root drive and then have vinum split things up? Given vinum is dependent on ufs, the corruption issue probably still holds true. Is there a choice - in other words have one big unix filesystem and use vinum to partition or have many unix partitions and each one is transitioned into a vinum volume? Sorry for long post - just lot's of things trying to figure out. Would appreciate any comments / advice on any particular point. Clearly a FreeBSD newbie, but been going through the books and trying to figure this thing out. Richard Fed up with RedHat and found the power of FreeBSD, but power = complexity. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tillman Sent: Sunday, July 27, 2003 9:03 AM To: [EMAIL PROTECTED] Subject: Re: FreeBSD5.1 Vinum Mirror root On Tue, Jul 22, 2003 at 09:57:23PM -0700, Richard Johannesson wrote: Is this second method outdate, or is there simply several ways to accomplish this task. I'm new to FreeBSD, so setting up vinum seems a little overwhelming. Just trying to mirror a 200GB root drive with another 200GB drive. Just out of curiosity, why would you want a 200GB root (/) file system? My sloppiest server consumes 54MB in /. -T -- The supreme irony of life is that hardly anyone gets out alive. - Robert Heinlein ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD5.1 Vinum Mirror root
Read everything I can find on vinum: vinum website, freebsd documentation on vinum, and Complete FreeBSD section on vinum. Still not sure which method is correct for setting up a mirrored root drive for a FreeBSD 5.1 system. The instructions I've found online regarding a vinum root drive, http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-root.html, does not mention any need to first install freebsd on a normal drive and then convert that root drive to a vinum drive. The instructions from the The Complete FreeBSD by Greg Lehey on installing FreeBSD5.1 on Vinum specifies to 1st do this freebsd install then convert to vinum. One thing this book mentions is to create the swap directory 1st so the vinum configuration will be stored in the 1st 265 sectors of the swap slice. Is this second method outdate, or is there simply several ways to accomplish this task. I'm new to FreeBSD, so setting up vinum seems a little overwhelming. Just trying to mirror a 200GB root drive with another 200GB drive. Would really appreciate any advice on this matter. Thanks, Richard ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD5.1 Vinum Mirror root
Actually there is one other source I found: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/ Good arcticle, but a little old so I'm guessing it's not appropriate for Rel 5.1 since vinum setup / support in 5.1 has been improved. Is this a bad assumption? Again, I'm just trying to figure which method is best to setup a mirrored root drive for FreeBSD 5.1. Thanks again, Richard -Original Message- From: Richard Johannesson [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 22, 2003 9:57 PM To: '[EMAIL PROTECTED]' Subject: FreeBSD5.1 Vinum Mirror root Read everything I can find on vinum: vinum website, freebsd documentation on vinum, and Complete FreeBSD section on vinum. Still not sure which method is correct for setting up a mirrored root drive for a FreeBSD 5.1 system. The instructions I've found online regarding a vinum root drive, http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-root.html, does not mention any need to first install freebsd on a normal drive and then convert that root drive to a vinum drive. The instructions from the The Complete FreeBSD by Greg Lehey on installing FreeBSD5.1 on Vinum specifies to 1st do this freebsd install then convert to vinum. One thing this book mentions is to create the swap directory 1st so the vinum configuration will be stored in the 1st 265 sectors of the swap slice. Is this second method outdate, or is there simply several ways to accomplish this task. I'm new to FreeBSD, so setting up vinum seems a little overwhelming. Just trying to mirror a 200GB root drive with another 200GB drive. Would really appreciate any advice on this matter. Thanks, Richard ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
