March 13, 201511 yr I'm getting a notification that I need to do an fsck on loop0 which based on the file system I assume is on my SNAP drive and has something to do with my docker image. Mar 12 14:38:46 NAS1 kernel: EXT4-fs (loop0): error count since last fsck: 54 Mar 12 14:38:46 NAS1 kernel: EXT4-fs (loop0): initial error at time 1410555868: ext4_lookup:1437: inode 31 Mar 12 14:38:46 NAS1 kernel: EXT4-fs (loop0): last error at time 1410804989: ext4_lookup:1437: inode 31 Does anyone know how I can run an fsck on this drive/file ? Edit: Looking more into the GUI, I see that my docker seems to be loop1 Label: none uuid: 3f2db28e-8d29-4793-b017-6019498a79ba Total devices 1 FS bytes used 2.17GiB devid 1 size 4.00GiB used 3.12GiB path /dev/loop1 Btrfs v3.18.2 so, I'm not sure how to find this.
March 14, 201511 yr I'm getting a notification that I need to do an fsck on loop0 which based on the file system I assume is on my SNAP drive and has something to do with my docker image. Mar 12 14:38:46 NAS1 kernel: EXT4-fs (loop0): error count since last fsck: 54 Mar 12 14:38:46 NAS1 kernel: EXT4-fs (loop0): initial error at time 1410555868: ext4_lookup:1437: inode 31 Mar 12 14:38:46 NAS1 kernel: EXT4-fs (loop0): last error at time 1410804989: ext4_lookup:1437: inode 31 Does anyone know how I can run an fsck on this drive/file ? Edit: Looking more into the GUI, I see that my docker seems to be loop1 Label: none uuid: 3f2db28e-8d29-4793-b017-6019498a79ba Total devices 1 FS bytes used 2.17GiB devid 1 size 4.00GiB used 3.12GiB path /dev/loop1 Btrfs v3.18.2 so, I'm not sure how to find this. If your running the kvm manager plugin, it uses a loopback image mounted at /etc/libvirt to store xml and settings for libvirt. The actual image is located at /boot/config/plugins/dynamix.kvm.manager/domain.img
March 14, 201511 yr Author Thanks, Do you know how to fsck it? can I run e2fsck against that img? I assume I need to bring down libvirt to do that?
March 15, 201511 yr Thanks, Do you know how to fsck it? can I run e2fsck against that img? I assume I need to bring down libvirt to do that? Yeah you should unmount it first. Stopping libvirt won't unmount it. umount /etc/libvirt. The run the check and repair. I would back it up first of course. e2fsck should work. Starting libvirt or going to the kvm page should load the image again.
March 20, 201511 yr Author Thanks dmacias, Finally got a chance to do this. I shut down docker/KVM/libvirt in settings, then manually unmounted /etc/libvirt. Made a copy of virtman.img, then ran e2fsck against it. Only thing of note, is I have the following file: boot/config/plugins/virtman/virtman.img not the one you listed, but it was what was mounted in /etc/libvirt. I also wasn't 100% sure how to answer all the questions. I did not create a lost&found but answered y to everything else. it is showing there are still errors... Not sure what, if anything I should do at this point. I brought everything back up and all seems ok. I havent' seen any syslog entries yet about the errors. root@NAS1:/boot/config/plugins/virtman# e2fsck virtman.img e2fsck 1.42.8 (20-Jun-2013) virtman.img contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Entry 'Windows7.xml' in /deleteme (31) has deleted/unused inode 54. Clear<y>? yes Pass 3: Checking directory connectivity /lost+found not found. Create<y>? no Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences: -(628--632) Fix<y>? yes Free blocks count wrong for group #0 (1319, counted=1324). Fix<y>? yes Free blocks count wrong (1319, counted=1324). Fix<y>? yes Inode bitmap differences: -54 Fix<y>? yes Free inodes count wrong for group #0 (130, counted=131). Fix<y>? yes Free inodes count wrong (130, counted=131). Fix<y>? yes virtman.img: ***** FILE SYSTEM WAS MODIFIED ***** virtman.img: ********** WARNING: Filesystem still has errors ********** virtman.img: 53/184 files (0.0% non-contiguous), 116/1440 blocks
Archived
This topic is now archived and is closed to further replies.