similar to: Vinum crash, advice needed

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

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 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, 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

Dear colleagues, experimenting with vinum stripes and mirrors, I'd stuck myself with the following: panic: throw_rude_remark: called without config lock (from vinumconfig.c:throw_rude_remark:103) The system before this panic has two 160G drives with two vinum partitions on each (one for mirrored root and one for the rest with swap between); these were ad0 and ad2. For the experiments,

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

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

Hello, At my work we have multiple freebsd machines running samba. Love it, things are working great. We have several windows 2000 servers that our engineers store their working drawings on. I need to create a mirror of this engineering windows 2000 machine to a freebsd machine running samba. The purpose of this is so that regular employees, welders whatever can just read the drawings on

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

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

Hello. I'm having a 4.7Rp9 server which is since months quite unstable, so I've compiled a debug kernel and got a crash dump. I'm a programmer and I know a little how to use gdb, I'm not so expert about FreeBSD kernel insides however, so I can't get much from it. Any kind of help is appreciated. This is the crash message: IdlePTD at phsyical address 0x0032f000 initial pcb

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

Hi all, I have some problems with my gvinum setup after the system panic'ed. Afterwards the system fails finding the plexes to the subdisks (or at least that is what I can understand after having searched the gvinum source code for the error string in the DMESG log..) The machine is an IBM Netfinity 5000 and the internal HW self tests does not find any errors in the hw. Luckily my root is

Hello freebsd-stable, I have 5.5-PRERELEASE server in production, booting from ad0s1: # BLOCKSIZE=512 swapinfo Device 512-blocks Used Avail Capacity /dev/ad0s1b 2097152 52872 2044280 3% /dev/ad1s1b 2097152 51952 2045200 2% Total 4194304 104824 4089480 2% # bsdlabel ad0s1 | fgrep b: b: 2097152 0 swap

Hello everyone, I have a 50-client Samba installation here (version of Samba is 3.0.12). The problem is, that files are not locked correctly. The scenario is the following: 1. User A opens a word document file and edits it 2. User B tries to open the same file, too 3. Instead of getting a warning that the file is in use by another user (like it was when we had NT4), Word opens the file without

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There has been a lot of discussion on these two mailing lists about the upcoming EoL of FreeBSD 4.x which I mentioned in my email entitled "HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon". Now that everybody (hopefully) has had their say, I'd like to offer some background and explanation. The concept of "security branches"

Hi, Recently I've decided to play with gjournal. Main reason was a promise of avoiding full fsck check after unclean shutdown. I've successfuly configured gjournal on existing filesystems (all UFS). And then it happened - my system had a power failure. After boot, it forced me to run fsck manualy. Nothing special, I did it before... But this time it failed on gjournaled disks.

I am using the following: Samba 2.2.8a (from FreeBSD ports) FreeBSD 4.7-RELEASE-p10 Samba is configured as a member of a Windows 2000 domain. Generally everything seems to be working as expected. Occasionally the following gets logged to the console: [2003/04/14 20:25:19, 0] smbd/service.c:make_connection(599) zulu (192.168.1.161) Can't change directory to /data/path (No such file or

Howdy all. We're experiencing some difficulties encountered from a new build/install world/kernel on a Compaq Proliant machine we have. We were running fine under 4.7-STABLE, and updated the sources to 4.8-STABLE last night (5/8/03), built and installed. This morning after a reboot, we got a horrid error to the likes of: Error mounting root. Error no 22. We encountered this error earlier

I've finally been able to capture the panic, as now it occurs even with DDB configured. Of the six machines I have running 6.1-RC (CVSupped today), this is the only one that does this. /boot/kernel/kernel text=0x30c488 data=0x3b6a0+0x3170c syms=[0x4+0x46430+0x4+0x58da4] no such file or directory - Hit [Enter] to boot immediately, or any other key for command prompt. Booting