Re: cautionary note about KT133 southbridge systems
Don't know if this will help or not but this problem was discussed at some length on various VIA HArdware sites. IIRC, it was tracked down to an incompatibility between the Southbridge and, of all things, the Soundblaster Live! sound card. Do you have such an animal in this machine? Either way, recent BIOS updates have come out to correct just this issue. You might want to try snagging one from your manufacturer. A BIOS upgrade certainly helped MY system out. Michael Perry wrote: >HI all- > >Awhile ago, I built a system which was destined to be my webserver which >was a AMD Duron 800 with the "fabled" Kt133a Southbridge chipset. AFter >numerous backups with amanda, I kept on getting i/o errors and strange >dump reports using an IBM 45 gig ATA 100 drive. On the system, the >drive was filled with dma retries and resets. I tried a whole bunch of >stuff to solve this including stepping the system down to no-DMA but >still had the problems. This was on a 2.4.13 kernel with the VIA ide >driver enabled; which usually fixes this sort of thing. At the end of >things, the drive started clanking on copying my build to a replacement >disk drive and I realized that the drive was probably gonna fail on me >at any moment. It also made me doubt that validity of backups since >each one seemed to have the strange dump reports in it but they all >completed. > >My main note here is to move carefully when using this particular >chipset and controller and different IDE drives. For me, any amount of >intensive disk io caused the system to burp out literally hundreds of >dma reset/retry errors. Replacing the drive with a Maxtor DiamondMax >80g drive solved the problems completely. > >If you see dma resets/retries when doing amanda dumps, you may want to >doublecheck what you are using as far as dma settings on the drive. > > -- -- Aaron Smith vox: 616.226.9550 Network Directorfax: 616.349.9076 Nexcerpt, Inc. [EMAIL PROTECTED]
cautionary note about KT133 southbridge systems
HI all- Awhile ago, I built a system which was destined to be my webserver which was a AMD Duron 800 with the "fabled" Kt133a Southbridge chipset. AFter numerous backups with amanda, I kept on getting i/o errors and strange dump reports using an IBM 45 gig ATA 100 drive. On the system, the drive was filled with dma retries and resets. I tried a whole bunch of stuff to solve this including stepping the system down to no-DMA but still had the problems. This was on a 2.4.13 kernel with the VIA ide driver enabled; which usually fixes this sort of thing. At the end of things, the drive started clanking on copying my build to a replacement disk drive and I realized that the drive was probably gonna fail on me at any moment. It also made me doubt that validity of backups since each one seemed to have the strange dump reports in it but they all completed. My main note here is to move carefully when using this particular chipset and controller and different IDE drives. For me, any amount of intensive disk io caused the system to burp out literally hundreds of dma reset/retry errors. Replacing the drive with a Maxtor DiamondMax 80g drive solved the problems completely. If you see dma resets/retries when doing amanda dumps, you may want to doublecheck what you are using as far as dma settings on the drive. -- Michael Perry | "Do or do not; there is no try" Master Yoda [EMAIL PROTECTED] | http://www.lnxpowered.org
disk relabeling
I have mislabled a disk but amanda has done dump to it. If i remove and relabel it, will i loose the backup? Hussain
Re: disk offline ?
Rainer Fuegenstein <[EMAIL PROTECTED]> wrote: > After adding a "new" old server named fav to amanda, I keep > getting the following message: > > FAILURE AND STRANGE DUMP SUMMARY: > fav/home2 lev 0 FAILED [disk /home2 offline on fav?] > > It doesn't matter if the disk is specified by device file or > mount directory: > > favc1t4d0s6tar-srv-low# /home2 > fav/home2 tar-srv-low# /home2 Looks familiar... Try to supply the absolute path for the obstinate drive. If that helps, we're two... hauke -- Hauke Fath /~\The ASCII tangro software components GmbH \ / Ribbon Campaign D-69115 Heidelberg X Against Ruf +49-6221-13336-0, Fax -21 / \ HTML Email!
Solved -- samba backups "offline"
About 2 weeks ago I asked the following: > I'm backing up a single W2K machine to my tape server. > There are 4 partitions on the windows box. Some nights > al 4 partitions are processed normally. Most nights > 1 or more of the partitions fail with the query > "host offline?" which obviously it is not as the other > partitions are backing up. I got a reply from Chris Marble that helped: > I'd try cranking down maxdumps for just that host. See if that helps. Rather than change the maxdumps parameter (which probably would have solved the problem) I chose to use the "spindle" feature and indicate each of the 4 partitions are on the "same spindle". Amanda limits the number of dumps on each spindle to 1 at a time. Since the change 10 days ago, not a single "offline" partition. Thanks Chris! -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
disk offline ?
Hi, After adding a "new" old server named fav to amanda, I keep getting the following message: FAILURE AND STRANGE DUMP SUMMARY: fav/home2 lev 0 FAILED [disk /home2 offline on fav?] It doesn't matter if the disk is specified by device file or mount directory: favc1t4d0s6tar-srv-low# /home2 fav/home2 tar-srv-low# /home2 backup works with all other disks: fav c1t5d0s5tar-srv-low# /home1 fav c1t2d0s6tar-srv-low# /mnt2 fav / tar-srv-low # / fav /usrtar-srv-low # /usr [...] mount reports: / on /dev/md/dsk/d0 read/write/setuid on Thu Dec 27 14:40:16 2001 /usr on /dev/md/dsk/d6 read/write/setuid on Thu Dec 27 14:40:16 2001 /proc on /proc read/write/setuid on Thu Dec 27 14:40:16 2001 /dev/fd on fd read/write/setuid on Thu Dec 27 14:40:16 2001 /var on /dev/md/dsk/d4 read/write/setuid on Thu Dec 27 14:40:16 2001 /tmp on swap read/write on Thu Dec 27 14:40:21 2001 /opt on /dev/md/dsk/d5 setuid/read/write on Thu Dec 27 14:40:21 2001 /usr/openwin on /dev/md/dsk/d3 setuid/read/write on Thu Dec 27 14:40:21 2001 /mnt1 on /dev/dsk/c1t5d0s6 setuid/read/write on Thu Dec 27 14:40:21 2001 /home2 on /dev/dsk/c1t4d0s6 setuid/read/write on Thu Dec 27 14:40:21 2001 /home1 on /dev/dsk/c1t5d0s5 setuid/read/write on Thu Dec 27 14:40:21 2001 /mnt2 on /dev/dsk/c1t2d0s6 setuid/read/write on Thu Dec 27 14:40:21 2001 I already had a look at the FAQ and I'm sure that: - the disk isn't to large (2 gigs total) - the file system isn't corrupted (fsck reports OK) - tar is used for backup, not dump. so there's the permission problem left, but I'm not really familiar with sun device files. after a quick look I had the impression that permissions are the same for all disk device files. tnx in advance. regards, rainer.
disk offline - addendum
sorry, I forgot OS is: SunOS fav 5.4 Generic_101945-43 sun4m sparc regards, rainer.
