Host-based backup of VMware vSphere VMs.
-
mcdaniels
- Enthusiast
- Posts: 49
- Liked: 5 times
- Joined: Mar 18, 2014 10:13 am
-
Contact:
Post
by mcdaniels »
this post
Hi,
I have got a linux-vm (ubuntu 20.04). After every Veeam Backup it reports:
Code: Select all
[1285016.802049] blk_update_request: critical target error, dev sda, sector 23596088 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
[1285094.114204] sd 2:0:0:0: [sda] tag#603 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[1285094.114209] sd 2:0:0:0: [sda] tag#603 Sense Key : Illegal Request [current]
[1285094.114210] sd 2:0:0:0: [sda] tag#603 Add. Sense: Invalid field in cdb
[1285094.114215] sd 2:0:0:0: [sda] tag#603 CDB: Write same(16) 93 08 00 00 00 00 01 68 0f 28 00 00 00 18 00 00
[1285094.114217] blk_update_request: critical target error, dev sda, sector 23596840 op 0x9:(WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
If I shut down the VM and restart it, the error is gone till the next Veeam Backup runs. Do you know what may be the cause of this?
Concerning "guest-processing" Application aware processing is not enabled.
Thanks!
-
david.domask
- Veeam Software
- Posts: 3064
- Liked: 710 times
- Joined: Jun 28, 2016 12:12 pm
-
Contact:
Post
by david.domask »
this post
Hi mcdaniels,
Are the VM disks thick provisioned by chance? Looks like
a known VMware behavior. Probably the snapshot created for backup triggers it.
David Domask | Product Management: Principal Analyst
-
mcdaniels
- Enthusiast
- Posts: 49
- Liked: 5 times
- Joined: Mar 18, 2014 10:13 am
-
Contact:
Post
by mcdaniels »
this post
Hi,
yes they are thick provisioned. Thanks for pointing me in the right direction.
so I will have to:
To use Thick Provisioned VMDKs, you need to disable the trim (discard) option on the relevant filesystems from within the guest OS.
But it is no harddisc // hardware failure at least.
Users browsing this forum: Semrush [Bot] and 73 guests