Bonjour,
j’ai une partition LVM créé avec lvcreate -n base-home -L 2G vg01
Où vg01 est le volume group (qui dispose de largement assez de place.
Je formate cette partition avec mkfs -t ext 4 /dev/mapper/vg01-base--home
Pas d’erreur.
Ensuite je monte la partition avec mount -t ext4 /dev/mapper/vg01-base--home /mnt/vm-part
Où /mnt/vm-part a été créé par mkdir /mnt/vm-part
mais si je fais ls -al /mnt/vm-part
j’obtiens l’erreur suivante:
# ls -al /mnt/vm-part
ls: lecture du répertoire '/mnt/vm-part': Message invalide
total 0
Et avec e2fsck:
# e2fsck -f -n /dev/mapper/vg01-base--tmp
e2fsck 1.46.2 (28-Feb-2021)
Resize inode not valid. Recreate? no
Pass 1: Checking inodes, blocks, and sizes
Inode 7, i_blocks is 12248, should be 8. Fix? no
Pass 2: Checking directory structure
Directory inode 2, block #0, offset 0: directory corrupted
Salvage? no
e2fsck: aborted
/dev/mapper/vg01-base--tmp: ********** WARNING: Filesystem still has errors **********
Alors que la même commande après le formatage ne donnait aucune erreur:
# e2fsck -f -n /dev/mapper/vg01-base--tmp
e2fsck 1.46.2 (28-Feb-2021)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/mapper/vg01-base--tmp: 11/131072 files (0.0% non-contiguous), 26156/524288 blocks
si je corrige les erreur de directory corrupted, tout revient à la normale.
# e2fsck -f /dev/mapper/vg01-base--tmp
e2fsck 1.46.2 (28-Feb-2021)
Resize inode not valid. Recreate<y>? yes
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory inode 2, block #0, offset 0: directory corrupted
Salvage<y>? yes
Missing '.' in directory inode 2.
Fix<y>? yes
Setting filetype for entry '.' in ??? (2) to 2.
Missing '..' in directory inode 2.
Fix<y>? yes
Setting filetype for entry '..' in ??? (2) to 2.
Directory inode 11, block #0, offset 0: directory corrupted
Salvage<y>? yes
Missing '.' in directory inode 11.
Fix<y>? yes
Setting filetype for entry '.' in ??? (11) to 2.
Missing '..' in directory inode 11.
Fix<y>? yes
Setting filetype for entry '..' in ??? (11) to 2.
Directory inode 11, block #1, offset 0: directory corrupted
Salvage<y>? yes
Directory inode 11, block #2, offset 0: directory corrupted
Salvage<y>? yes
Directory inode 11, block #3, offset 0: directory corrupted
Salvage<y>? yes
Pass 3: Checking directory connectivity
'..' in / (2) is <The NULL inode> (0), should be / (2).
Fix<y>? yes
Unconnected directory inode 11 (/???)
Connect to /lost+found<y>? yes
/lost+found not found. Create<y>? yes
Pass 3A: Optimizing directories
Pass 4: Checking reference counts
Inode 11 ref count is 3, should be 2. Fix<y>? yes
Pass 5: Checking group summary information
Block bitmap differences: +8487
Fix<y>? yes
Free blocks count wrong for group #0 (24282, counted=24283).
Fix<y>? yes
Free blocks count wrong (498133, counted=498134).
Fix<y>? yes
/dev/mapper/vg01-base--tmp: ***** FILE SYSTEM WAS MODIFIED *****
/dev/mapper/vg01-base--tmp: 12/131072 files (0.0% non-contiguous), 26154/524288 blocks
# mount -t ext4 /dev/mapper/vg01-base--tmp /mnt/vm-part
# ls -al /mnt/vm-part/
total 12
drwxr-xr-x 3 root root 4096 4 août 13:28 .
drwxr-xr-x 5 root root 4096 2 août 13:37 ..
drwx------ 3 root root 4096 4 août 13:45 lost+found
Toutes les commandes sont faite en tant que root (pas de sudo)
je ne comprends pas où est le problème…