Re: AVerMedia AVerTV Hybrid+FM Cardbus
> <[EMAIL PROTECTED]> writes: > bktr.ko is for Conexant (formerly Rockwell) Booktree (Fussion) > 8x8/8x9 based cards and you have Philips saa713x based, so you > should try with the correct driver and applications. You can > download them from here: > http://download.purpe.com/ > I don't know why the driver from the link above is not > included, like bktr.ko, into the FreeBSD, and if it will work > with your device, but with my saa7134 based ECS EZ-TV (TVP3XP) > TV&FM Tuner card, everything works great and I am able to watch > analog TV and capture under FreeBSD 5.x : > [EMAIL PROTECTED]:11:0: class=0x048000 card=0x4cb41019 chip=0x71341131 > rev=0x01 hdr=0x00 vendor = 'Philips Semiconductors' device = > 'SAA7134HL Multi Media Capture Device' class = multimedia after applying proposed driver I get: [EMAIL PROTECTED]:0:0: class=0x048000 card=0xf4361461 chip=0x71331131 rev=0xd1 hdr=0x00 vendor = 'Philips Semiconductors' device = 'SAA7135HL Multi Media Capture Device' class= multimedia and running ftvv application in source Tab after pressing Tune Channels I get: Error changing to frequency: 48.25: Input/output error and in the log appears: iicbus0: START: bus error (status 0x9 loop:13) Here is the kldstat output: Id Refs AddressSize Name 1 23 0xc040 380600 kernel 21 0xc0781000 64cc linprocfs.ko 32 0xc0788000 1b40clinux.ko 42 0xc07a4000 1d4fcsound.ko 51 0xc07c2000 5a44 snd_ich.ko 61 0xc07c8000 8740 ng_ubt.ko 72 0xc07d1000 dd4c netgraph.ko 81 0xc07df000 580b4acpi.ko 91 0xc27d2000 3000 est.ko 101 0xc29cf000 17000radeon.ko 111 0xc3801000 2c000nfsclient.ko 121 0xc6e38000 8000 saa.ko 132 0xc6e4 3000 iicbus.ko 141 0xc6e54000 3000 iic.ko Anyone any hints what could be wrong? Thanks. Regards, lk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
AVerMedia AVerTV Hybrid+FM Cardbus
Hello, I am using FreeBSD RELENG_5 and decided to give a try to video capture device. From the friend, I've got AVerMedia AVerTV Hybrid+FM Cardbus. When I plug it to my notebook I get the following to the log: cardbus0: Resource not specified in CIS: id=10, size=800 cardbus0: at device 0.0 (no driver attached) and after kldload bktr.ko: bktr_mem: memory holder loaded Here is the pciconf -lv output: . [EMAIL PROTECTED]:0:0: class=0x048000 card=0xf4361461 chip=0x71331131 rev=0xd1 hdr=0x00 vendor = 'Philips Semiconductors' device = 'SAA7135HL Multi Media Capture Device' class= multimedia Is anybody running this card? Am I doing something wrong? Is there another driver for the card? I did not find anything useful searching the archives. Regards, lk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ahd scsi adapter problem on 5.4-STABLE
Hello all, could somebody help me to identify problem on FreeBSD 5.4-STABLE? I am not sure if it is SCSI adapter problem or disk problem. Thank you very much. Regards, lk # dmesg LQIRetry for LQICRCI_LQ to release ACK ahd0: Transmission error detected LQISTAT1[0x10] LASTPHASE[0x1] SCSISIGI[0x60] PERRDIAG[0x4] >> Dump Card State Begins < ahd0: Dumping Card State at program address 0x1 Mode 0x33 Card was paused INTSTAT[0x8] SELOID[0x9] SELID[0x30] HS_MAILBOX[0x0] INTCTL[0x80] SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x30] SCSISIGI[0x76] SCSIPHASE[0x0] SCSIBUS[0x51] LASTPHASE[0x1] SCSISEQ0[0x0] SCSISEQ1[0x12] SEQCTL0[0x10] SEQINTCTL[0x0] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x0] KERNEL_QFREEZE_COUNT[0x0] MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x0] SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4] LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x80] LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x81] SCB Count = 16 CMDS_PENDING = 1 LASTSCB 0x6 CURRSCB 0x6 NEXTSCB 0x0 qinstart = 6 qinfifonext = 6 QINFIFO: WAITING_TID_QUEUES: Pending list: 5 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0x3f] Total 1 Kernel Free SCB list: 6 12 1 2 3 4 7 8 9 10 11 13 14 15 0 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: Sequencer On QFreeze and Complete list: ahd0: FIFO0 Free, LONGJMP == 0x829e, SCB 0x6 SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] ahd0: FIFO1 Free, LONGJMP == 0x809e, SCB 0x0 SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] LQIN: 0x4 0x8 0x0 0x5 0x0 0x2 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x24 0x0 0x0 0x0 0x0 ahd0: LQISTATE = 0x2b, LQOSTATE = 0x0, OPTIONMODE = 0x42 ahd0: OS_SPACE_CNT = 0x1f MAXCMDCNT = 0x1 ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 SIMODE0[0xc] CCSCBCTL[0x0] ahd0: REG0 == 0x6, SINDEX = 0x133, DINDEX = 0x114 ahd0: SCBPTR == 0xff06, SCB_NEXT == 0xff00, SCB_NEXT2 == 0x0 CDB 6 1 0 0 0 0 STACK: 0x140 0x1b 0x140 0x1b 0x140 0x1b 0x140 0x1 < Dump Card State Ends >> LQIRetry for LQICRCI_LQ to release ACK ahd0: Transmission error detected LQISTAT1[0x10] LASTPHASE[0x1] SCSISIGI[0x60] PERRDIAG[0x4] >> Dump Card State Begins < ahd0: Dumping Card State at program address 0xa9 Mode 0x33 Card was paused INTSTAT[0x8] SELOID[0x9] SELID[0x30] HS_MAILBOX[0x0] INTCTL[0x80] SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x30] SCSISIGI[0x76] SCSIPHASE[0x0] SCSIBUS[0x51] LASTPHASE[0x1] SCSISEQ0[0x0] SCSISEQ1[0x12] SEQCTL0[0x10] SEQINTCTL[0x80] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x0] KERNEL_QFREEZE_COUNT[0x0] MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x0] SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4] LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x80] LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x81] SCB Count = 16 CMDS_PENDING = 1 LASTSCB 0x6 CURRSCB 0x6 NEXTSCB 0x0 qinstart = 6 qinfifonext = 6 QINFIFO: WAITING_TID_QUEUES: Pending list: 5 FIFO_USE[0x0] SCB_CONTROL[0x40] SCB_SCSIID[0x3f] Total 1 Kernel Free SCB list: 6 12 1 2 3 4 7 8 9 10 11 13 14 15 0 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: Sequencer On QFreeze and Complete list: ahd0: FIFO0 Free, LONGJMP == 0x829e, SCB 0x6 SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] ahd0: FIFO1 Free, LONGJMP == 0x809e, SCB 0x0 SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] LQIN: 0x4 0x8 0x0 0x5 0x0 0x2 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x24 0x0 0x0 0x0 0x0 ahd0: LQISTATE = 0x2b, LQOSTATE = 0x0, OPTIONMODE = 0x42 ahd0: OS_SPACE_CNT = 0x1f MAXCMDCNT = 0x1 ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 SIMODE0[0xc] CCSCBCTL[0x0] ahd0: REG0 == 0x6, SINDEX = 0x133, DINDEX = 0x114 ahd0: SCBPTR == 0xff06, SCB_NEXT == 0xff00, SCB_NEXT2 == 0x0 CDB 6 1 0 0 0 0 STACK: 0x1 0x140 0x1b 0x140 0x1b 0x140 0x1b 0x140 < Dump Card State Ends >> LQIRetry for LQICRCI_LQ to release ACK ahd0: Transmission error detected LQISTAT1[0x10] LASTPHASE[0x1] SCSISIGI[0x60] PERRDIAG[0x4] >> Dump Card State Begins < ahd0: Dumping Card State at program address 0xaa Mode 0x33 Card was paused INTSTAT[0x8] SELOID[0x9] SELID[0x30] HS_MAILBOX[0x0] INTCTL[0x80] SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x30] SCSISIGI[0x76] SCSIPHASE[0x0] SCSIBUS[0x51
Re: gvinum: adding plex and subdisks to existing volume
> On 23 dec 2005, at 15:25, Ludo Koren wrote:
>>>>>>> Arno Beekman <[EMAIL PROTECTED]> writes:
>>
>>> On 18 dec 2005, at 18:24, Ludo Koren wrote:
>>
>>>> Any help appreciated, I cannot find useful hints.
>>>>
>>
>>> http://www.vinumvm.org/ http://www.freebsddiary.org/vinum.php
>>> man 4 vinum man 8 vinum
>>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-
>>> vinum.html http://devel.reinikainen.net/docs/how-to/Vinum/
>> maybe I was not enough specific. There is not enough
>> information about gvinum in the case. All you've mentioned is
>> about vinum and there are some diffrences; not all commands are
>> implemented... BTW, the addition of disk on 5.4-STABLE is
>> causing panic. I posted the problem to the
>> [EMAIL PROTECTED]
>>
>> Regards,
>>
>> lk
>>
> hi Ludo,
> gvinum = vinum anything you need to do to add a new drive which
> is written on those sites can be done for gvinum as well... at
> least that's my experience
http://wikitest.freebsd.org/moin.cgi/GvinumManPage
specifically BUGS:
gvinum(8) does not yet fully implement all functions found in
vinum(4). Specifically, the following commands from vinum(4) are not
supported:
...
> if you follow the descriptions of replacing a disk and get
> panics there might be something else that's wrong
lk
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gvinum: adding plex and subdisks to existing volume
>>>>> Arno Beekman <[EMAIL PROTECTED]> writes: > On 18 dec 2005, at 18:24, Ludo Koren wrote: >> Any help appreciated, I cannot find useful hints. >> > http://www.vinumvm.org/ http://www.freebsddiary.org/vinum.php > man 4 vinum man 8 vinum > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum- > vinum.html http://devel.reinikainen.net/docs/how-to/Vinum/ maybe I was not enough specific. There is not enough information about gvinum in the case. All you've mentioned is about vinum and there are some diffrences; not all commands are implemented... BTW, the addition of disk on 5.4-STABLE is causing panic. I posted the problem to the [EMAIL PROTECTED] Regards, lk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gvinum: adding plex and subdisks to existing volume
Hi, I'm using 5.4-STABLE. One of the mirrored disks died. I want to add new disk, which has not the same size as the died one. The output of the gvinum l is the following: # gvinum l 4 drives: D rd2 State: up /dev/da2s1h A: 0/1023 MB (0%) D d2State: up /dev/da2s1f A: 0/15452 MB (0%) D d3State: up /dev/da3s1A: 0/70001 MB (0%) D d4State: up /dev/da1s1A: 0/70001 MB (0%) 2 volumes: V root State: up Plexes: 1 Size: 1023 MB V usr State: up Plexes: 2 Size: 83 GB 4 plexes: P usr.p0 C State: down Subdisks: 1 Size: 68 GB P usr.p1 C State: up Subdisks: 2 Size: 83 GB P root.p1 C State: up Subdisks: 1 Size: 1023 MB P root.p0 C State: down Subdisks: 0 Size: 0 B 6 subdisks: S usr.p0.s0 State: down D: d1 Size: 15 GB S usr.p1.s0 State: up D: d2 Size: 15 GB S root.p1.s0State: up D: rd2 Size: 1023 MB S root.p0.s0State: down D: rd1 Size: 1023 MB S usr.p0.s1 State: up D: d3 Size: 68 GB S usr.p1.s1 State: up D: d4 Size: 68 GB and # camcontrol devlist -v scbus0 on ahd0 bus 0: at scbus0 target 3 lun 0 (pass0,da0) at scbus0 target 9 lun 0 (pass1,da1) at scbus0 target 10 lun 0 (sa0,pass2) < > at scbus0 target -1 lun -1 () scbus1 on ahd1 bus 0: at scbus1 target 1 lun 0 (pass3,da2) at scbus1 target 8 lun 0 (pass4,da3) < > at scbus1 target -1 lun -1 () scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) I want to have the whole new disk a one vinum slice so the # disklabel da0s1 # /dev/da0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 143363700 2814.2BSD0 0 0 c: 1433639970unused0 0 # "raw" part, don't edit h: 143363981 16 vinum The old one was: # disklabel da2s1 # /dev/da2s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 2096855 2814.2BSD 2048 16384 0 b: 2097152 2097152 swap c: 358409520unused0 0 # "raw" part, don't edit f: 31646648 4194304 vinum h: 2097136 16 vinum When I try to do: # gvinum create gvinum.conf it ends up in immediate panic (page fault). The gvinum.conf file: drive d1b device /dev/da0s1h plex name usr.p2 org concat vol usr plex name root.p2 org concat vol root sd name root.p2.s0 drive d1b len 2096871s driveoffset 265s plex root.p2 plexoffset 0s sd name usr.p2.s0 drive d1b len 31646383s driveoffset 2097136s plex usr.p2 plexoffset 0s Am I doing something wrong? How can be added a new disk to existing mirror in gvinum? Any help appreciated, I cannot find useful hints. Regards, lk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gvinum + swap on 5.4-STABLE
Hello, is it possible to use swap on vinum volume? I know there was some problems on earlier 5.x version with vinum. Thanks, lk PS: I cannot find anything on the topic in the mail archive... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
gvinum + growfs on 5.4-STABLE
Hi, is it possible (tested?) to use safely growfs on gvinum mirror volume on FreeBSD 5.4-STABLE ? (I know there was problem on earlier 5.x version with vinum). Thanks, lk PS: I did not search yet, but has anybody step by step docs on replacing a dead drive in gvinum mirror? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
GUS UltraSound on FreeBSD 5.4-STABLE
Hi, anyone successfully configured and used GUS UltraSound on FreeBSD 5.4-STABLE, recently? I have device sound device snd_gusc in the kernel config and hint.gusc.0.at="isa" hint.gusc.0.port="0x220" hint.gusc.0.irq="15" hint.gusc.0.drq="5" in the /boot/device.hints, but during verbose booting I only get: gusc0 failed to probe at port 0x320-0x327,0x220 irq 15 drq 5 on isa0 I was using the card on 4.X, but since I upgraded to FreeBSD 5.X branch (about a year ago) I didn't use it. I set the irq and drq with DOS setgus.exe utility. Any hints appreciated. Thank you very much. Regards, lk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Backup on DDS-4 tapes
> Ludo Koren wrote: >> It doesn't help either... The result is the same. >> >> > Just to check I'm understanding your problem correctly -- > you're expecting to write much more data to the tape than is > actually being written. That's right. I suppose that 54GB of data could fit on 2 40GB tapes... > If that's correct, then there's a couple things I can think of: > 1) Your tape drive isn't doing hardware compression. Check the > manual and see if there are any dip switches you need to set. > (Make a note of how they're set before you change anything, so > you can go back to what you had originally!). I'll check this > When you say the result is the same, if it used exactly the > same number of tapes (down to the decimal point) then that > definitely suggests that your tape drive is not compressing. > 2) The data you're writing to the tape is already mostly > compressed, so you won't fit as much as you might if it were > uncompressed data. I will do statistics about files. > Also, the 40Gb per tape that you quote is, I think, the MAXIMUM > amount of data the tape will take. It's only 20Gb native. > 40Gb is how much will fit at optimum compression, which you > never get. > It's unlikely to be a FreeBSD problem because I regularly fit > 6-7Gb on a DDS-2, which has a native size of 4Gb. I use dump > options like the ones in my last message. > --Alex Thank, for your suggestions. lk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Backup on DDS-4 tapes
>> # /sbin/dump -Lu0 -B 41943040 -C 32 -f /dev/sa0 /usr >> >> >> > I would guess that your tape drive does hardware compression in > which case the amount of data which fits on a tape is variable. > In such a case you can't tell dump how big the tape is -- I > haven't used options like -B since 1600bpi reel-to-reel tapes, > except in my day you specified how many feet of tape you had > :-) > from man dump > -a ``auto-size''. Bypass all tape length considerations, > and enforce writing until an end-of-media indication is > returned. This fits best for most modern tape drives. Use of > this option is particularly recommended when appending to an > existing tape, or using a tape drive with hardware compression > (where you can never be sure about the compression ratio). It doesn't help either... The result is the same. > Don't know -L, must be a 5.x thing. Try: -L This option is to notify dump that it is dumping a live file sys- tem. To obtain a consistent dump image, dump takes a snapshot of the file system in the .snap directory in the root of the filesystem being dumped and then does a dump of the snapshot. The snapshot is removed when the dump is complete. If the .snap directory does not exist in the root of the filesystem being dumped, the dump will fail. This problem can be corrected by creating a .snap directory in the root of the filesystem to be dumped; its owner should be root, its group should be operator, and its mode should be 0770. > /sbin/dump -Lu0 -a -C 32 -f /dev/sa0 /usr > I use -b 64 as well. > Use cpio/tar at your peril as they may not do devices right and > may not understand filesystem flags. > --Alex lk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Backup on DDS-4 tapes
> --pP0ycGQONqsnqIMP Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > On Monday, 14 March 2005 at 10:38:02 +0100, Ludo Koren wrote: >> Hi, >> >> I am using 5.2.1-RELEASE-p3 for backup on DDS-4 tapes 40GB in >> size. >> >> ... >> >> Why I cannot dump the filesystem on 2 tapes (it takes 3, it >> seems it works without compression) no matter if I use dump or >> cpio? What I am doing wrong? > You're using dump :-) > Dump is too stupid to understand compression or EOF marks, so > it errs on the side of caution. It's also IMO not a very good > backup medium unless you really want the incremental dump > facility. Even between different releases of FreeBSD there are > compatibility problems, and you can assume that there is no > compatibility at all between different operating systems. You > may find tar a better choice. Surprisingly http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/backup-basics.html in 16.1.7 suggests dump, though as the reference is used (maybe) outdated E. Zwicky link... Anyway, cpio cannot handle the problem too, and the tar in 5.2.1-RELEASE-p3 can handle multi-volume backup, but in the 5.3-STABLE don't according to the man page. I wonder what is then the best solution. Regards, lk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Backup on DDS-4 tapes
Hi, I am using 5.2.1-RELEASE-p3 for backup on DDS-4 tapes 40GB in size. # df -k Filesystem 1K-blocks UsedAvail Capacity Mounted on /dev/vinum/root 1016162 157405 77746517%/ devfs 110 100%/dev /dev/vinum/usr 84746248 54467390 2349916070%/usr procfs 440 100%/proc # camcontrol devlist -v scbus0 on ahd0 bus 0: at scbus0 target 3 lun 0 (pass0,da0) at scbus0 target 9 lun 0 (pass1,da1) at scbus0 target 10 lun 0 (sa0,pass2) < > at scbus0 target -1 lun -1 () scbus1 on ahd1 bus 0: at scbus1 target 1 lun 0 (pass3,da2) at scbus1 target 8 lun 0 (pass4,da3) < > at scbus1 target -1 lun -1 () scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) # /sbin/dump -SLu0 -B 41943040 -C 32 -f /dev/sa0 /usr DUMP: Date of this level 0 dump: Mon Mar 14 10:29:51 2005 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping snapshot of /dev/vinum/usr (/usr) to /dev/sa0 DUMP: mapping (Pass I) [regular files] DUMP: Cache 32 MB, blocksize = 65536 DUMP: mapping (Pass II) [directories] DUMP: estimated 54189311 tape blocks on 1.29 tape(s). # # mt -f /dev/sa0 status Mode Density Blocksize bpi Compression Current: 0x26:DDS-4 variable 97000DCLZ -available modes- 0:0x26:DDS-4 variable 97000DCLZ 1:0x26:DDS-4 variable 97000DCLZ 2:0x26:DDS-4 variable 97000DCLZ 3:0x26:DDS-4 variable 97000DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 0 Residual Count 0 I am using the following command: # /sbin/dump -Lu0 -B 41943040 -C 32 -f /dev/sa0 /usr or # /sbin/dump -aLu0 -C 32 -f /dev/sa0 /usr Why I cannot dump the filesystem on 2 tapes (it takes 3, it seems it works without compression) no matter if I use dump or cpio? What I am doing wrong? Any hints appreciated. Thank you very much in advance. Regards, lk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: growfs on vinum volume
>>> It has 'historical' reason. I started with vinum, when it was >>> not possible to mirror root partition (at least I found just >>> document 'Bootstrapping Vinum: A Foundation for Reliable >>> Servers' by R. A. Van Valzah in 2001 or 2002 on >>> www.freebsd.org) >> There has never been any reason to have more than one drive per >> module. You're confusing drives and subdisks. > I think he meant that he original had a root partition and a > vinum partition, and later converted the root partition to > another vinum partition. Exactly. That I meant by 'historical' reason. > =2D-=20 Kirk Strauser lk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: growfs on vinum volume
>>> What you do now depends on the state of the file system. >>> Hopefully you still have the original contents. In this case, >> Yes, I have original contents. The volume size is 15GB just as >> before. > OK. You've seen le's message. No. Probably, I missed it. lk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: growfs on vinum volume
>> >> vinum -> l ... >> D d1State: up /dev/da1s1e A: 0/15452 MB (0%) >> D rd1 State: up /dev/da1s1h A: 0/1023 MB (0%) > You shouldn't have more than one drive per spindle. It has 'historical' reason. I started with vinum, when it was not possible to mirror root partition (at least I found just document 'Bootstrapping Vinum: A Foundation for Reliable Servers' by R. A. Van Valzah in 2001 or 2002 on www.freebsd.org) >> ... >> growfs /dev/vinum/mirror > You've missed out some information. May I assume that you had > a valid file system on the 15 GB volume mirror before you > started this? Yes >> It finished with the following error: >> >> growfs: bad inode number 1 to ginode >> >> I have searched the archives, but did not find any >> answer. Please, could you point to me what I did wrong? > You trusted growfs on 5.2.1 :-) I did it successfully before on 5.x (I don't remember exactly, about 6 months ago) but not on vinum volume... > growfs is suffering from lack of love, and presumably you had a > UFS 2 file system on the drive. It's only recently been fixed > for that, in 5-CURRENT. There is UFS 1 file system on the drive. > What you do now depends on the state of the file system. > Hopefully you still have the original contents. In this case, Yes, I have original contents. The volume size is 15GB just as before. > you could get hold of the version from -CURRENT, which should > compile with no problems, and try again. It wouldn't do any > harm to take down one of the plexes so that you can recover if > something goes wrong. Thank you very much for your advice. I'll try it on weekend, because there is no possible downtime during the working days. > Greg lk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
growfs on vinum volume
Hi list on 5.2.1-RELEASE-p3, I did: fdisk -BI da2 fdisk -BI da3 and disklabel -e da2s1 disklabel -e da3s1 # /dev/da2s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 143363981 16unused0 0 c: 1433639970unused0 0 # "raw" part, don't edit h: 1433639970 vinum # /dev/da3s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 143363981 16unused0 0 c: 1433639970unused0 0 # "raw" part, don't edit h: 1433639970 vinum vinum create vinumgrow vinumgrow: drive d3 device /dev/da2s1h drive d4 device /dev/da3s1h sd name mirror.p0.s1 drive d3 plex mirror.p0 size 0 sd name mirror.p1.s1 drive d4 plex mirror.p1 size 0 after vinum -> start mirror.p0.s1 and vinum -> start mirror.p1.s1 I have vinum -> l 6 drives: D d1State: up /dev/da1s1e A: 0/15452 MB (0%) D rd1 State: up /dev/da1s1h A: 0/1023 MB (0%) D d2State: up /dev/da0s1f A: 0/15452 MB (0%) D rd2 State: up /dev/da0s1h A: 0/1023 MB (0%) D d3State: up /dev/da2s1h A: 0/70001 MB (0%) D d4State: up /dev/da3s1h A: 0/70001 MB (0%) 2 volumes: V mirrorState: up Plexes: 2 Size: 83 GB V root State: up Plexes: 2 Size: 1023 MB 4 plexes: P mirror.p0 C State: up Subdisks: 2 Size: 83 GB P mirror.p1 C State: up Subdisks: 2 Size: 83 GB P root.p1 C State: up Subdisks: 1 Size: 1023 MB P root.p0 C State: up Subdisks: 1 Size: 1023 MB 6 subdisks: S mirror.p0.s0 State: up D: d1 Size: 15 GB S mirror.p1.s0 State: up D: d2 Size: 15 GB S root.p1.s0State: up D: rd2 Size: 1023 MB S root.p0.s0State: up D: rd1 Size: 1023 MB S mirror.p0.s1 State: up D: d3 Size: 68 GB S mirror.p1.s1 State: up D: d4 Size: 68 GB vinum -> which seems to be correct... Than I did growfs /dev/vinum/mirror It finished with the following error: growfs: bad inode number 1 to ginode I have searched the archives, but did not find any answer. Please, could you point to me what I did wrong? Thank you very much. lk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
