xe vm-disk-add device=<disk position number> disk-size=< KiB, MiB, GiB or TiB> sr-uuid=<SR-UUID> vm=<VM-UUID>
You can change the name of the disk from XenCenter.
xe vm-disk-add device=<disk position number> disk-size=< KiB, MiB, GiB or TiB> sr-uuid=<SR-UUID> vm=<VM-UUID>
You can change the name of the disk from XenCenter.
When Unitrends creates snapshots, it copies the snap shots to the Unitrends storage and then deletes the snapshot. If the delete operation fails, then every time Unitrends creates a snapshot the snapshot chain will grow in size. The snapshot chain has a maximum size of 30 snapshots. After the 30th snapshot no more can be created. The error, “Snapshot chain is too long” will appear in the Unitrends logs. You will also not be able to create a snapshot in XenCenter or from an xe command
Workaround:
We can add only one big disk to the master image as the system drive, and we can split the disk to multiple partition as we like in the master image.
After I create the Ghost 3.0 boot disk for USB drive, what is the function in the disk(except imaging)?
Can I use gdisk and partitioning?
This article describes the filesystems supported for on-access scanning on Linux platforms.
The following sections are covered:
Known to apply to the following Sophos product(s) and version(s)
Sophos Anti-Virus for Linux 9 and Sophos Anti-Virus for Linux 10
The following filesystems are known to work with Sophos Anti-Virus for Linux:
Filesystem Name | Talpa Support? | Fanotify Support? |
---|---|---|
btrfs | Yes | Yes |
cifs | Yes | No |
ecryptfs | Yes | Yes |
ext2 | Yes | Yes |
ext3 | Yes | Yes |
ext4 | Yes | Yes |
fuse | Yes | Yes |
fuseblk | Yes | Yes |
iso9660 | Yes | Yes |
jfs | Yes | Yes |
minix | Yes | Yes |
msdos | Yes | Yes |
ncpfs | Yes | Yes |
nfs | Yes | Yes |
nfs4 | Yes* | No |
nssadmin | Yes | No |
oes | Yes | No |
overlayfs | Yes | Yes |
overlay | Yes | Yes |
ramfs | Yes | Yes |
reiserfs | Yes | Yes |
smbfs | Yes | Yes |
tmpfs | Yes | Yes |
udf | Yes | Yes |
vfat | Yes | Yes |
xfs | Yes | Yes |
zfs | Yes | No |
*Note: Talpa does not support locally mounted (non-network) nfs4 filesystems.
The following filesystems are unsupported. The majority of these are pseudo-filesystems that do not contain regular files and cannot be scanned.
Filesystem Name | Talpa Support? | Fanotify Support? | Notes |
---|---|---|---|
aufs | No | No | Pseudo-filesystem |
autofs | No | No | Pseudo-filesystem |
binfmt_misc | No | No | Pseudo-filesystem |
bpf | No | No | Pseudo-filesystem |
cgroup | No | No | Pseudo-filesystem |
configfs | No | No | Pseudo-filesystem |
debugfs | No | No | Pseudo-filesystem |
devfs | No | No | Pseudo-filesystem |
devpts | No | No | Pseudo-filesystem |
devtmpfs | No | No | Pseudo-filesystem |
fuse.gvfs-fuse-daemon |
No | No | See KBA 118982 |
fusectl | No | No | Pseudo-filesystem |
inotifyfs | No | No | Pseudo-filesystem |
mqueue | No | No | Pseudo-filesystem |
nfsd | No | No | Pseudo-filesystem |
nsspool | No | No | Pseudo-filesystem |
proc | No | No | Pseudo-filesystem |
romfs | No | No | Pseudo-filesystem |
rootfs | No | No | Pseudo-filesystem |
rpc_pipefs | No | No | Pseudo-filesystem |
securityfs | No | No | Pseudo-filesystem |
selinuxfs | No | No | Pseudo-filesystem |
squashfs | No | No | |
subfs | No | No | Pseudo-filesystem |
sysfs | No | No | Pseudo-filesystem |
usbdevfs | No | No | Pseudo-filesystem |
usbfs | No | No | Pseudo-filesystem |
Behavior with other filesystems will depend on the on-access interception method:
If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.
This is invaluable for us to ensure that we continually strive to give our customers the best information possible.
This article provides information about how Sophos Anti-Virus for Linux modifies the atime and mtime of a given file after it has been scanned with savscan.
Applies to the following Sophos product(s) and version(s)
Sophos Anti-Virus for Linux
## atime
# ls -lu --full-time /tmp/folder/
-rw-r--r-- 1 root root 107 <date> 15:30:46.492277736 +0900 file001
## mtime
# ls -l --full-time /tmp/folder/
-rw-r--r-- 1 root root 107 <date> 15:30:46.491277717 +0900 file001
## ctime
# ls -lc --full-time /tmp/folder/
-rw-r--r-- 1 root root 107 <date> 15:30:46.493277755 +0900 file001
The timestamp for the atime
and mtime
is reset to the millisecond value of .000000000
# savscan /tmp/folder/
SAVScan virus detection utility
Version 5.5X.Y [Linux/AMD64]
Virus data version 5.XY, Month Year
Includes detection for 30928050 viruses, Trojans and worms
Copyright (c) 1989-2019 Sophos Limited. All rights reserved.
<timestamp>
IDE directory is: /opt/sophos-av/lib/sav
Using IDE file [..]
Quick Scanning
1 file scanned in 19 seconds.
No viruses were discovered.
End of Scan.
## atime
# ls -lu --full-time /tmp/folder/
-rw-r--r-- 1 root root 107 <date> 15:30:46.000000000 +0900 file001
## mtime
# ls -l --full-time /tmp/folder/
-rw-r--r-- 1 root root 107 <date> 15:30:46.000000000 +0900 file001
## ctime
# ls -lc --full-time /tmp/folder/
-rw-r--r-- 1 root root 107 <date> 15:35:11.171369753 +0900 file001
Note: The above example shows that the atime
and mtime
values for a file are rounded down to the nearest second.
If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.
This is invaluable for us to ensure that we continually strive to give our customers the best information possible.
Good afternoon,
I am having problem sms 10.7.0-5, after command monitor disk other_free is full. How to clear space from this partition?
thank you
Good morning, Inside the company i work for we got many cnc siemens machines with a pc windows 7 and the ghost suite integrated. After a blackuot i made a backup of the 2 partitions contained inside the ssd and after that i tried to restore an old partition backup. Here i made an error, i pressed restore entire hdd and i choose the partition file. After 2 seconds i got an error from the ghost console. Now, i got the hdd without anything inside. I think the procedure canceled some configuration files but no real files. Windows does not start and during the boot up i only got a black screen. Do you know any way to try to recover the hdd?
Hi guys,
We’re trying to update our win10 master and captured our customized installation. We don’t have any problem with the capture, no errors or warning. When I try to create a deployment task (using a copy of the one we use for our 1803 master), I can add the *.gho I’ve just created. But when I go to the advanced options for resizing partitions, none are listed (I should have 3 listed). The 3 partitions are created if I use the *.gho but I really need to resize them.
Does someone here ever encountered this problem ? What am I missing ? Thanks for your help !