On Apr 30, 2018, at 12:27 PM, RAJESH DASARI <raajeshdasari@xxxxxxxxx> wrote: > > Hi , > > We are noticing an issue with logical volume file system is getting > corrupted after restarting the machine for multiple times. > > This issue we have started noticing after upgrading the kernel to 4.4.121. > > while running tune2fs -c 1 /dev/VG_NEW/state to set the > mmax_mounts_count we are noticing the error. > > tune2fs -c 1 /dev/VG_NEW/state > tune2fs 1.44.0 (7-Mar-2018) > tune2fs: The ext2 superblock is corrupt while trying to open /dev/VG_NEW/state > Couldn't find valid filesystem superblock. > > lvs command output is below (there are other logical volumes and > volume groups also along with state volume, I have not pasted them to > minimize this post). > Important thing to note here is always state volume only is getting > corrupted and no file system corruption seen on other logical volumes. Are you sharing this volume group between multiple hosts/VMs or similar? Cheers, Andreas > lvs > > LV VG > Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync > Convert > > state VG_NEW > -wi-a----- 1000.00m > > blkid command output is below > > blkid > /dev/mapper/VG_NEW--state: LABEL="state" > UUID="57f82106-3fd2-4d8c-9cbe-676dc58d5405" SEC_TYPE="ext2" > TYPE="ext3" > /dev/mapper/VG_NEW--backup: LABEL="backup" > UUID="2771bdac-f005-4bde-88a1-5ace80faa89f" SEC_TYPE="ext2" > TYPE="ext3" > /dev/mapper/VG_NEW--ErrorInformation: LABEL="ErrorInformati" > UUID="e5f18c5a-aec8-498a-8feb-b81686bf2ff9" SEC_TYPE="ext2" > TYPE="ext3" > > please find the output of mount command. > > mount -o noatime -t ext4 /dev/VG_NEW/state /mnt/state > [ 271.786492] EXT4-fs (dm-0): ext4_check_descriptors: Block bitmap > for group 0 not in group (block 64)! > [ 271.795731] EXT4-fs (dm-0): group descriptors corrupted! > mount: mounting /dev/VG_NEW/state on /mnt/state failed: Structure needs cleaning > -bash-4.4# > > when i tried to recover , recovery was successful but after multiple > reboots we have seen this issue again. > please find the output of e2fsck > > e2fsck -f -y /dev/VG_NEW/state > e2fsck 1.44.0 (7-Mar-2018) > ext2fs_open2: The ext2 superblock is corrupt > e2fsck: Superblock invalid, trying backup blocks... > 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 > Free blocks count wrong for group #0 (28095, counted=24283). > Fix? yes > > Free blocks count wrong for group #2 (32266, counted=32128). > Fix? yes > > Free blocks count wrong for group #6 (32266, counted=32029). > Fix? yes > > Free blocks count wrong (243372, counted=243370). > Fix? yes > > Free inodes count wrong for group #0 (7989, counted=7988). > Fix? yes > > Free inodes count wrong for group #2 (8000, counted=7829). > Fix? yes > > Directories count wrong for group #2 (0, counted=37). > Fix? yes > > Free inodes count wrong for group #6 (8000, counted=7881). > Fix? yes > > Directories count wrong for group #6 (0, counted=52). > Fix? yes > > Free inodes count wrong (63700, counted=63698). > Fix? yes > > > state: ***** FILE SYSTEM WAS MODIFIED ***** > state: 302/64000 files (2.6% non-contiguous), 12630/256000 blocks > -bash-4.4# > > Could you please suggest what could be the cause for this issue. > Please provide pointers on how to proceed. > > > > Thanks, > Rajesh Dasari. Cheers, Andreas
Attachment:
signature.asc
Description: Message signed with OpenPGP
