Re: 12 TB btrfs file system on virtual machine broke again

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Jan 5, 2020 at 12:52 PM Christian Wimmer
<telefonchris@xxxxxxxxxx> wrote:
>
> BTW, I found this messages in the messages-20200105 file:
>
>
>
> bash$ grep fstrim messages-20200105
> 2019-12-23T00:00:03.533050-03:00 linux-ze6w fstrim[32008]: fstrim: /boot/grub2/i386-pc: FITRIM ioctl failed: Input/output error
> 2019-12-23T00:00:04.354989-03:00 linux-ze6w fstrim[32008]: fstrim: /boot/grub2/x86_64-efi: FITRIM ioctl failed: Input/output error
> 2019-12-23T00:00:05.149687-03:00 linux-ze6w fstrim[32008]: fstrim: /home: FITRIM ioctl failed: Input/output error
> 2019-12-23T00:00:05.941978-03:00 linux-ze6w fstrim[32008]: fstrim: /opt: FITRIM ioctl failed: Input/output error
> 2019-12-23T00:00:06.740810-03:00 linux-ze6w fstrim[32008]: fstrim: /root: FITRIM ioctl failed: Input/output error
> 2019-12-23T00:00:07.523365-03:00 linux-ze6w fstrim[32008]: fstrim: /srv: FITRIM ioctl failed: Input/output error
> 2019-12-23T00:00:08.361831-03:00 linux-ze6w fstrim[32008]: fstrim: /tmp: FITRIM ioctl failed: Input/output error
> 2019-12-23T00:00:09.188937-03:00 linux-ze6w fstrim[32008]: fstrim: /usr/local: FITRIM ioctl failed: Input/output error
> 2019-12-23T00:00:09.974086-03:00 linux-ze6w fstrim[32008]: fstrim: /var: FITRIM ioctl failed: Input/output error
> 2019-12-23T00:00:10.761933-03:00 linux-ze6w fstrim[32008]: fstrim: /: FITRIM ioctl failed: Input/output error

Bet these are all on /dev/sda2 file system.

> 2019-12-23T00:00:10.762050-03:00 linux-ze6w fstrim[32008]: /mnt/so_logic: 27.1 GiB (29089808384 bytes) trimmed on /dev/sdd1
> 2019-12-23T00:00:10.762121-03:00 linux-ze6w fstrim[32008]: /home/chris2: 265.4 GiB (284938117120 bytes) trimmed on /dev/sdc1

I can't tell what file system or device these are on, but it appears
to succeed without error. Therefore the VM is advertising discard
support to the guest. But what is calling fstrim? It appears to not be
fstrim.timer. We still don't know whether it might be the cause of
problems elsewhere in the storage stack that might explain why the
Btrfs file system you care about is being corrupted.



> 2019-12-23T00:00:10.762538-03:00 linux-ze6w systemd[1]: fstrim.service: Failed with result 'exit-code'.
> 2020-01-03T11:30:45.742369-03:00 linux-ze6w fstrim[27910]: fstrim: /boot/grub2/i386-pc: FITRIM ioctl failed: Input/output error

10 days.

"weekly" for systemd timers means "monday at 00:00" local time. Which
is what you're seeing in the first line, but not the second.




-- 
Chris Murphy



[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux