Re: rdiff-backup memory problems

[Matthew Dale Moore]

On Wednesday 07 May 2008 11:58:20 am David wrote:
> Also, I don't trust rdiff-backup as much as I do rsync. It seems a bit
> too complicated/fragile by comparison. Rsync is very robust, simple,
> and works every time. The only reason I use rdiff-backup is because of
> it's reverse delta support. I would prefer to replace rdiff-backup if
> possible, rather than rsync.

If you are looking for a replacement, I don't know of any that do rdiffs 
besides rdiff-backup. I think that a good incremental backup would be your 
best option.

It looks like all the stuff with making the hardlinks and temp directory are 
to avoid a potential conflict between the existing "rdiff-backup-data" 
directory on backup1 and the other "rdiff-backup-data" directory that gets 
written to on backup2. If backup1 and backup2 both have rdiff-backup 
installed then you can do something like

rdiff-backup backup1::/backup/files /backup/path/on/backup2 --exclude 
**rdiff-backup-data**

on backup2. This avoids making hardlinks and a temp directory and also avoids 
your problem of having the two "rdiff-backup-data" directories conflicting.

MM


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: rdiff-backup memory problems

[Matthew Dale Moore]

I read you CLUG post. It seems like you should be able to do everything that 
you want using rdiff-backup and not using your temp work directory with rsync 
(which looks to be messing things up).

Also, if you are using rdiff-backup on backup1, why do you need to preserve 
file history on backup2? Shouldn't the copy of backup1 on backup2 also 
contain the rdiff-backup-data directory? If this is the case then you can 
just use rsync to move the backup from backup1 to backup2.

MM


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: DVD drive misbehaves after a while, kernel problem?

[Matthew Dale Moore]

On Tuesday 18 December 2007 03:43:00 pm Mirko Parthey wrote:
> After between 10 and 60 minutes of uptime, my DVD drive begins to show
> strange behaviour:
>
> - an icon appears on the KDE desktop showing either a data CD-ROM
>   or an audio CD (although the tray is empty and closed)
>
> - in /var/log/kern.log, these messages appear in large numbers:
>
> Dec 18 10:28:00 guitar2 kernel: hda: cdrom_pc_intr: The drive appears
> confused (ireason = 0x01). Trying to recover by ending request. Dec 18
> 10:28:00 guitar2 kernel: hda: status error: status=0x58 { DriveReady
> SeekComplete DataRequest } Dec 18 10:28:00 guitar2 kernel: ide: failed
> opcode was: unknown Dec 18 10:28:00 guitar2 kernel: hda: drive not ready
> for command Dec 18 10:28:02 guitar2 kernel: hda: status error: status=0x58
> { DriveReady SeekComplete DataRequest } Dec 18 10:28:02 guitar2 kernel:
> ide: failed opcode was: unknown
>
> At this stage, the drive becomes unusable, while it it is working fine
> otherwise. A reboot "fixes" the problem, until the next occurence.

[snip]

> my hardware:
> - PLEXTOR DVDR PX-760A, firmware 1.07
>  (restored to original Plextor firmware for this bug report)
> - mainboard Gigabyte 965P-S3, with this IDE controller:
>   03:00.1 IDE interface: JMicron Technologies, Inc. JMicron 20360/20363
> AHCI Controller (rev 02)

I am experiencing this same problem since Jan 2007. I have the same 
motherboard but a different DVD-RW drive. When I first attempted to install 
linux on my newly built computer, the damned JMicron controller was 
unsupported, and so DVD drive access was impossible. About 3 weeks later 
support was added, and I have always figured that this behavior is a symptom 
of just poor support for this controller. 

A workaround that I have been using for the past few months is just to keep a 
blank CD-RW (or some kind of media) in the drive at all times. It seems like 
this only happens when the drive is empty for more than a few minutes.

I would be interested in any advice anyone has to offer.

MM


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]