I am studying this Red Hat documentation, which states that a validated storage pool should have a lost+found directory to indicate that it is properly mounted.  I have followed the instructions from the documentation explicitly, but yet my results (shown below) do not include a lost+found directory.  Has this storage pool been properly mounted?  What else needs to be done in order for the storage pool described below to validate correctly?  Otherwise, if the below is validated as properly mounted, then please explain the underlying reasons.Create and Start/AutoStart the Storage Pool:[root@remote-host ~]# virsh pool-define-as eighthPool fs - - /dev/mapper/centos-eighth - /eighthPoolPool eighthPool defined[root@remote-host ~]# virsh pool-build eighthPoolPool eighthPool built[root@remote-host ~]# virsh pool-start eighthPoolPool eighthPool started[root@remote-host ~]# virsh pool-autostart eighthPoolPool eighthPool marked as autostartedValidate the Storage Pool:[root@remote-host ~]# virsh pool-list --all Name                 State      Autostart------------------------------------------- eighthPool           active     yes home                 active     yes root                 active     yes someUserName         active     yes tmp                  active     yes[root@remote-host ~]# virsh pool-info eighthPoolName:           eighthPoolUUID:           230c3939-b009-4d28-97ff-09419492cd9bState:          runningPersistent:     yesAutostart:      yesCapacity:       224.89 GiBAllocation:     32.20 MiBAvailable:      224.85 GiB[root@remote-host ~]# mount | grep /eighthPool/dev/mapper/centos-eighth on /eighthPool type xfs (rw,relatime,seclabel,attr2,inode64,noquota)[root@remote-host ~]# ls -la /eighthPooltotal 4drwxr-xr-x.  2 root root    6 Mar 12 11:03 .dr-xr-xr-x. 25 root root 4096 Mar 20 08:23 ..[root@remote-host ~]#Other Contents Of The Physical Disk:For reference, the partitions of the hard disk prior to creating the new storage pool are listed as follows:  [root@remote-host ~]# fdisk -lWARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.Disk /dev/sda: 2000.4 GB, 2000398934016 bytes, 3907029168 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytesDisk label type: gpt#         Start          End    Size  Type            Name 1         2048       411647    200M  EFI System      EFI System Partition 2       411648      1435647    500M  Microsoft basic 3      1435648   3897165823    1.8T  Linux LVMDisk /dev/mapper/centos-root: 53.7 GB, 53687091200 bytes, 104857600 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytesDisk /dev/mapper/centos-swap: 8187 MB, 8187281408 bytes, 15990784 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytesDisk /dev/mapper/centos-home: 241.6 GB, 241591910400 bytes, 471859200 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytes....Other extraneous stuff omitted for brevity.Disk /dev/mapper/centos-eighth: 241.6 GB, 241587716096 bytes, 471851008 sectorsUnits = sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 4096 bytesI/O size (minimum/optimal): 4096 bytes / 4096 bytes
Why is there no lost+found directory in storage pool?
rhel;partition;kvm;storage;virsh