similar to: vinum (root on vinum too) throw_rude_remark crash: endless loop

Dear colleagues, [I'm under 4-STABLE] What is the correct sequence to delete existing vinum module (for example, raid10) and do *not* use -f flags for vinum? in my case t is raid10 vovume: vinum -> l -r t V t State: up Plexes: 2 Size: 8191 MB P t.p0 S State: up Subdisks: 2 Size: 8191 MB P t.p1 S State:

Hi there, sorry for rather long mail. Two verbose dmesgs and `pciconf -vl` outputs attached. trying to set up new machine based on ASUS P4BGL-MX motherboard, I'd encountered hangs after detecting pcib1 (ICH2). MB has rl 8100 ethernet chip onboard. This is for 4.8-R; however, machine hangs in very similar way also with 4.4-R and 5.1-R. Matrix of hangs: Onboard Ether External Ether Result

Well, colleagues, I'm stuck a bit. I tried many different ways to setup system with vinum root (the only reference I found yet besides old "bootstrapping vinum" article is Joerg's commit message: http://freebsd.rambler.ru/bsdmail/cvs-all_2003/msg01225.html I failed. I have 4-stable system set up at ad0, and tried to set up pair of drives for new system at ad2 and ad3 (actually,

Dear collagues, could someone sched me a light about the following crash (I'm almost sure about hardware, temperature, etc...) Machine is fairly stable; however, there are occational crashes, similar to this one; backtraces are almost always single-step. It's 4.8-R, dmesg and gdb -k output follows ====================================================================================

I've just had a 4.9p1 system partially deadlock for about 30 minutes and then spontaneously(?) recover. The "ps" results point at vinum. I've never seen this before and don't recall anything like this being mentioned here before. At the time, I had two find's running in a large NFS mounted filesystem and was doing a "cvs -d /usr/ncvs -R checkout -P ports" from

I made an array out of 3 IBM 20 gigs and 3 Maxtor 20 gigs I used striping to make one big drive A couple of days ago I was copying a movie onto to it and the computer decided to reboot when it came back up I was greeted with this message Can someone please tell me if I can recover some how? or should I just rebuild the array? or is one of my disks physically bad? Detects all 7 drives (1 10gig

I am trying to setup vinum on a box using 4.8 RELENG_4 (as of about a week ago snapshot). This box was running 4.6 /w vinum on same hard drives for the last 4 months wonderfully... but since it is my current 'scratch/backup' box, I just reinstalled with -STABLE. # uname -a FreeBSD polya.axista.com 4.8-STABLE FreeBSD 4.8-STABLE #22: Tue Jun 24 17:01:07 EDT 2003

Hi, I'm not sure this is supposed to happen (my computer rebooted halfway through adding an other drive to a volume): [long lines needed] (02:44:50 <~>) 0 $ sudo vinum ld D storage State: up Device /dev/ad0d Avail: 38166/381 66 MB (100%) D worthless State: up Device /dev/ad2d Avail: 38038/380 38 MB (100%) D barracuda

FreeBSD 4.1.1-RELEASE #1: Tue Oct 10 18:09:51 CDT 2000 root@test-drive.tamu.edu:/usr/src/sys/compile/TEST-DRIVE Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CM

Hi, I had a power failure, and the on-disk configuration for vinum went bizarre. The logs read from disks are at http://biaix.org/pk/debug/ (log.$DEVICE files). The logs in da0 (barracuda) are the ones obviously wrong, I'm pretty sure the others are ok. Is this a 'virtually' dead drive? Can I force vinum to use the other's drive configuration? What's the less traumatic

I have same problem on same class machine, here is dmesg from failing boot (via serial console): -------------------- Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.8-RELEASE-p7 #0: Sat Sep 20 17:07:38 EEST 2003

Hi all, I got a machine with 8GB of RAM and plenty of disk space. I need gvinum to manage big number of file systems but PAE enabled kernel does not compile modules. I couldn't figure out how to get vinum statically compiled in the kernel if that is the way to go. I am running 6-STABLE. Please advise on how to get PAE kernel and gvinum working together! TIA, Stoyan

Hello, I'm having problems getting my samba setup to work at a little LAN i partially maintain. I've been reading quite a lot about what I could think of being related to my problems/setup, and I've also googled my ass off :( So here I am, resorting to you guys in hope of help =] Sorry to say, but I don't have much experience, and therefore I'm a bit lost at the moment. Not

Hi All, I'm about to clean and re-initialize a Maxtor 160GB disk that shows a weird problem but I think I've found a bug in RELENG_4_7 somewhere so if preserving my disk can help conquer one more bug I'm happy to wait a couple of days and help solve that bug. Here's the story: While upgrading from 4.3-STABLE to 4.7p4 and at the same time reorganizing my vinum volumes I copied

Dear colleagues, I'm planning to debug usb connection with my new SONY CLIE handheld, and found that this process is much complicated by the fact usb.ko module can not be unloaded 'cause some process is referencing it: marck@revamp:~/tmp> kldstat -v -i 11 Id Refs Address Size Name 11 1 0xc0cf7000 1b000 usb.ko Contains modules: Id Name

Dear colleagues, in the process of upgrading my home router I'm trying to utilise Intel D2500CC mini-ITX motherboard[1]. Both stable/9 and head suffer from no scrolling issue: from the beginning of booting the kernel, all output overrides the last line on the screen, while others keep the loader phase. Provided the board has multiple serial ports and the final target (headless

Colleagues, 3 of 4 times this machine failed to boot, panicing somewhere in late kernel initialization phase (before /sbin/init is executed) I have serial console and KDB enabled, so can do experiments. Last two crashes: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8 fault code = supervisor read data, page not present instruction pointer =

Dear collegaues, please evaluate the patch attached, which allow to use both --detect-renamed and --fileflags extra features. This is meta-patch which sould be applied to detect-renamed. fileflags patch should be applied first, following by the modified detect-renamed patch. It is included in current FreeBSD port, but it seems it would be much more useful to be supported by samba

Pawel, another one (though minor, I suppose) bug report: while playing with my poor pool, I tried to interact with it on -current, thus importing it with -f (without upgrading, of course). After reverting to RELENG_7, I found I no more can access history: root@moose:~# /usr/obj/usr/src/cddl/sbin/zpool/zpool history History for 'm': 2008-10-14.23:04:28 zpool create m raidz ad4h ad6h

I am trying to upgrade my system from 4.7RELEASE to 4.8STABLE. I have followed the instructions from the manual: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html Right now, I am on step 21.4.8 Reboot into Single User Mode. I have compiled my new kernel, and I was trying to reboot into single user mode to test the new kernel. When I do this, I get the following error