Linux proxy logging something interesting

[mikeely]

Trying out the linux proxy for direct NFS repo and when the job is starting up I get a lot of this in syslog:

Code: Select all

Jan 28 13:23:10 a.vpx kernel: vmw_pvscsi: msg type: 0x0 - MSG RING: 1/0 (5) 
Jan 28 13:23:10 a.vpx kernel: vmw_pvscsi: msg: device added at scsi0:1:0
Jan 28 13:23:10 a.vpx kernel: scsi 0:0:1:0: Direct-Access     VMware   Virtual disk     1.0  PQ: 0 ANSI: 2
Jan 28 13:23:10 a.vpx kernel: sd 0:0:1:0: [sdb] 167772160 512-byte logical blocks: (85.8 GB/80.0 GiB)
Jan 28 13:23:10 a.vpx kernel: sd 0:0:1:0: [sdb] Write Protect is off
Jan 28 13:23:10 a.vpx kernel: sd 0:0:1:0: [sdb] Mode Sense: 61 00 00 00
Jan 28 13:23:10 a.vpx kernel: sd 0:0:1:0: [sdb] Cache data unavailable
Jan 28 13:23:10 a.vpx kernel: sd 0:0:1:0: [sdb] Assuming drive cache: write through
Jan 28 13:23:10 a.vpx kernel: sd 0:0:1:0: Attached scsi generic sg2 type 0
Jan 28 13:23:10 a.vpx kernel: sdb: sdb1 sdb2
Jan 28 13:23:10 a.vpx kernel: sd 0:0:1:0: [sdb] Attached SCSI disk
Jan 28 13:23:12 a.vpx kernel: ata1: soft resetting link
Jan 28 13:23:12 a.vpx kernel: ata1: EH complete

The "hard resetting link/SATA link down (SStatus 0 SControl 300)/EH complete" cycles through ata1 through ata32 and does this for each drive being backed up. Seems pretty spammy.

At the end this appears:

Code: Select all

Jan 28 13:34:05 a.vpx kernel: vmw_pvscsi: msg type: 0x1 - MSG RING: 3/2 (5) 
Jan 28 13:34:05 a.vpx kernel: vmw_pvscsi: msg: device removed at scsi0:2:0
Jan 28 13:34:05 a.vpx kernel: vmw_pvscsi: failed to lookup scsi0:2:0
Jan 28 13:34:34 a.vpx kernel: vmw_pvscsi: msg type: 0x1 - MSG RING: 4/3 (5) 
Jan 28 13:34:34 a.vpx kernel: vmw_pvscsi: msg: device removed at scsi0:1:0
Jan 28 13:34:34 a.vpx kernel: vmw_pvscsi: failed to lookup scsi0:1:0

So is the above normal expected stuff or is it an indication of failure? The test backup job ran just fine, but our syslog monitor tripped on the messages so here I am asking. If it's expected how can we quiet it, or is it just something we should set the monitor to ignore - I hate doing that because it's an excellent way to miss ongoing trouble.

[HannesK]

Hello,
as far as I read the, there is no problem.

I'm sure that there is a way to configure syslog in a way that Veeam messages get into an extra file. As I don't see which syslog you are using, I suggest to search the internet or ask in the forum / communication channel of your distribution.

Personal opinion: it's just a proxy. I wouldn't care as long backup speed & restore is fine and successful.

Best regards,
Hannes