Determine DomU disk usage under Xen Dom0

Judging the disk usage of DomU under Xen Dom0 is roughly known from xentop: CPU %, MEM %, network, I/O... but for the use of DomU disks, such as: how much inode is used, how much space is left, whether the flash is full or whether the customer should be notified to upgrade the Xen hard disk is insufficient. [root @ Rocky ~] # Xentop use dumpe2fs here to eliminate sorrow for you. Although it is not very accurate, it will not be too outrageous. [plain] <pre name = "code" class = "plain"> [root @ localhost ~] # Dumpe2fs-h/dev/xvda1 dumpe2fs 1.39 (29-May-2006) Filesystem volume name:/Last mounted on: <not available> Filesystem UUID: Invalid Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr limit dir_index filetype limit sparse_super large_file Default mount options: Using acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: linux Inode count: 767232 Block count: 767095 Reserved block count: 38354 Free blocks: 439490 Free inodes: 716246 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 187 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 31968 Inode blocks per group: 999 Filesystem created: Tue Apr 9 01:07:47 2013 Last mount time: tue Apr 9 09:44:18 2013 Last write time: Tue Apr 9 09:44:18 2013 Mount count: 3 Maximum mount count:-1 Last checked: Tue Apr 9 01:07:47 2013 Check interval: 0 (<none>) Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 128 Journal inode: 8 First orphan inode: 171042 Default directory hash: tea Directory Hash Seed: 839d1c07-6fc3-4794-9526-92d5ef94fa19 Journal backup: inode blocks Journal size: 64 M </pre> <br> from: Inode count, Block count, free blocks, Free inodes, Block size, etc. can be used to determine the disk usage