Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 3474

Filesystemproblems (critical errors) after restore of VMWARE Snapshot

$
0
0
Hi folks,
although this is a Debian running @ VMWARE ESXI I have a question. Perhaps its more ESXI related, but at least it is the filesystem running on debian making trouble ;-)

I took a snapshop of a debianserver in running state.
I then reverted to the snapshot also in running state.

Now I got numerous messages (syslog) looking like:

Code:

blk_update_request: critical target error, dev sda, sector 36097424 op 0x9WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0[462603.391549] sd 2:0:0:0: [sda] tag#44 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE[462603.391551] sd 2:0:0:0: [sda] tag#44 Sense Key : Illegal Request [current] 462603.391551] sd 2:0:0:0: [sda] tag#44 Add. Sense: Invalid field in cdb[462603.391552] sd 2:0:0:0: [sda] tag#44 CDB: Write same(16) 93 08 00 00 00 00 02 26 a8 08 00 00 00 28 00 00[462603.391553] blk_update_request: critical target error, dev sda, sector 36087816 op 0x9WRITE_ZEROES) flags 0x800 phys_seg 0 prio class 0
So it seems like it was no good idea to take and revert so snapshot in running state, cause now there seems to be a filesystem-problem. I should have turned off the vm before taking the snapshot and reverting to the snapshot.

If you let the snapshotthing out of the context: What can I do in this scenario? fschk from Rescue-media? The system still runs without problems (which makes me wonder a little bit)

Filesystem is ext4

Any hint is very welcome.

Statistics: Posted by mcdaniels — 2025-02-06 15:53 — Replies 0 — Views 30



Viewing all articles
Browse latest Browse all 3474

Trending Articles