search for: jlixfeld

...# meetme.conf [rooms] conf => 97531,24680 # extensions.conf [conf] exten => 1,1,Answer exten => 1,2,Wait(1) exten => 1,3,Authenticate(5447847) exten => 1,4,MeetMe(97531,Mas,24680) exten => 1,5,Playback(vm-goodbye) exten => 1,6,Hangup() exten => 2,1,MeetMe(97531,Ms,24680) [jlixfeld@trek://~ ]$ kldstat Id Refs Address Size Name 1 5 0xc0400000 5e16d8 kernel 2 4 0xc231e000 2f000 zaptel.ko 3 1 0xc234f000 6000 wcfxo.ko 4 1 0xc2355000 a000 wcfxs.ko 5 1 0xc235f000 2000 ztdummy.ko [jlixfeld@trek://~ ]$

...# meetme.conf [rooms] conf => 97531,24680 # extensions.conf [conf] exten => 1,1,Answer exten => 1,2,Wait(1) exten => 1,3,Authenticate(5447847) exten => 1,4,MeetMe(97531,Mas,24680) exten => 1,5,Playback(vm-goodbye) exten => 1,6,Hangup() exten => 2,1,MeetMe(97531,Ms,24680) [jlixfeld@trek://~ ]$ kldstat Id Refs Address Size Name 1 5 0xc0400000 5e16d8 kernel 2 4 0xc231e000 2f000 zaptel.ko 3 1 0xc234f000 6000 wcfxo.ko 4 1 0xc2355000 a000 wcfxs.ko 5 1 0xc235f000 2000 ztdummy.ko [jlixfeld@trek://~ ]$

An EXT3 filesystem technically isn't supposed to require an fsck, correct? Well, as per my last email re: EXT3 Crash?! I ran an fsck on a couple of my LVMs. It said they were clean, but then I decided to be 100% sure and force an fsck. Error after Error after Error after Error. I wound up losing almost half the data on my LVM due to all the errors. What's the real deal? Am I doing

Just wondering if someone could help me debug this: I was moving data from an ATARAID (via Promise FastTrack100 Controller) into the LVM device below: 58,1: # cat /proc/lvm/VGs/foo3/LVs/bar name: /dev/foo3/bar size: 476315648 access: 3 status: 1 number: 0 open: 1 allocation: 0 device: 58:01 # /sbin/pvscan pvscan -- reading all physical volumes