All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Wimmer <telefonchris@icloud.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>, Qu WenRuo <wqu@suse.com>,
	Anand Jain <anand.jain@oracle.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: 12 TB btrfs file system on virtual machine broke again
Date: Sun, 5 Jan 2020 16:52:16 -0300	[thread overview]
Message-ID: <BF92D4FB-0FBF-49F8-A32D-60D56C41AAEC@icloud.com> (raw)
In-Reply-To: <CAJCQCtS+a2WU01QCHXycLT8ktca-XV5JkO-KwtjRRzeEa4xikQ@mail.gmail.com>

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
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
2019-12-23T00:00:10.762198-03:00 linux-ze6w systemd[1]: fstrim.service: Main process exited, code=exited, status=64/n/a
2019-12-23T00:00:10.762449-03:00 linux-ze6w systemd[1]: fstrim.service: Unit entered failed state.
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
2020-01-03T11:30:46.592336-03:00 linux-ze6w fstrim[27910]: fstrim: /boot/grub2/x86_64-efi: FITRIM ioctl failed: Input/output error
2020-01-03T11:30:47.476629-03:00 linux-ze6w fstrim[27910]: fstrim: /home: FITRIM ioctl failed: Input/output error
2020-01-03T11:30:48.376543-03:00 linux-ze6w fstrim[27910]: fstrim: /opt: FITRIM ioctl failed: Input/output error
2020-01-03T11:30:49.295675-03:00 linux-ze6w fstrim[27910]: fstrim: /root: FITRIM ioctl failed: Input/output error
2020-01-03T11:30:50.180612-03:00 linux-ze6w fstrim[27910]: fstrim: /srv: FITRIM ioctl failed: Input/output error
2020-01-03T11:30:51.049373-03:00 linux-ze6w fstrim[27910]: fstrim: /tmp: FITRIM ioctl failed: Input/output error
2020-01-03T11:30:51.919945-03:00 linux-ze6w fstrim[27910]: fstrim: /usr/local: FITRIM ioctl failed: Input/output error
2020-01-03T11:30:52.777132-03:00 linux-ze6w fstrim[27910]: fstrim: /var: FITRIM ioctl failed: Input/output error
2020-01-03T11:30:53.623997-03:00 linux-ze6w fstrim[27910]: fstrim: /: FITRIM ioctl failed: Input/output error
2020-01-03T11:30:53.624172-03:00 linux-ze6w fstrim[27910]: /mnt/so_logic: 27.1 GiB (29089808384 bytes) trimmed on /dev/sdd1
2020-01-03T11:30:53.624247-03:00 linux-ze6w fstrim[27910]: /home/chris2: 262.5 GiB (281862184960 bytes) trimmed on /dev/sdc1
2020-01-03T11:30:53.624365-03:00 linux-ze6w systemd[1]: fstrim.service: Main process exited, code=exited, status=64/n/a
2020-01-03T11:30:53.624883-03:00 linux-ze6w systemd[1]: fstrim.service: Unit entered failed state.
2020-01-03T11:30:53.624991-03:00 linux-ze6w systemd[1]: fstrim.service: Failed with result 'exit-code'.


Chris


  parent reply	other threads:[~2020-01-05 19:52 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06  3:44 [PATCH] btrfs-progs: Skip device tree when we failed to read it Qu Wenruo
2019-12-06  6:12 ` Anand Jain
2019-12-06 15:50   ` Christian Wimmer
2019-12-06 16:34   ` Christian Wimmer
     [not found]   ` <762365A0-8BDF-454B-ABA9-AB2F0C958106@icloud.com>
2019-12-07  1:16     ` Qu WenRuo
2019-12-07  3:47       ` Christian Wimmer
2019-12-07  4:31         ` Qu Wenruo
2019-12-07 13:03           ` Christian Wimmer
2019-12-07 14:10             ` Qu Wenruo
2019-12-07 14:25               ` Christian Wimmer
2019-12-07 16:44               ` Christian Wimmer
2019-12-08  1:21                 ` Qu WenRuo
2019-12-10 21:25                   ` Christian Wimmer
2019-12-11  0:36                     ` Qu Wenruo
2019-12-11 15:57                       ` Christian Wimmer
     [not found]           ` <9FB359ED-EAD4-41DD-B846-1422F2DC4242@icloud.com>
2020-01-04 17:07             ` 12 TB btrfs file system on virtual machine broke again Christian Wimmer
2020-01-05  4:03               ` Chris Murphy
2020-01-05 13:40                 ` Christian Wimmer
2020-01-05 14:07                   ` Martin Raiber
2020-01-05 14:14                     ` Christian Wimmer
2020-01-05 14:23                       ` Christian Wimmer
2020-01-05  4:25               ` Qu Wenruo
2020-01-05 14:17                 ` Christian Wimmer
2020-01-05 18:50                   ` Chris Murphy
2020-01-05 19:18                     ` Christian Wimmer
2020-01-05 19:36                       ` Chris Murphy
2020-01-05 19:49                         ` Christian Wimmer
2020-01-05 19:52                         ` Christian Wimmer [this message]
2020-01-05 20:34                           ` Chris Murphy
2020-01-05 20:36                             ` Chris Murphy
     [not found]                         ` <3F43DDB8-0372-4CDE-B143-D2727D3447BC@icloud.com>
2020-01-05 20:30                           ` Chris Murphy
2020-01-05 20:36                             ` Christian Wimmer
2020-01-05 21:13                               ` Chris Murphy
2020-01-05 21:58                                 ` Christian Wimmer
2020-01-05 22:28                                   ` Chris Murphy
2020-01-06  1:31                                     ` Christian Wimmer
2020-01-06  1:33                                     ` Christian Wimmer
2020-01-11 17:04                                     ` 12 TB btrfs file system on virtual machine broke again (third time) Christian Wimmer
2020-01-11 17:23                                     ` Christian Wimmer
2020-01-11 19:46                                       ` Chris Murphy
2020-01-13 19:41                                         ` 12 TB btrfs file system on virtual machine broke again (fourth time) Christian Wimmer
2020-01-13 20:03                                           ` Chris Murphy
2020-01-31 16:35                                             ` btrfs not booting any more Christian Wimmer
2020-05-08 12:20                                             ` btrfs reports bad key ordering after out of memory situation Christian Wimmer
2020-01-05 23:50                   ` 12 TB btrfs file system on virtual machine broke again Qu Wenruo
2020-01-06  1:32                     ` Christian Wimmer
2020-01-11  7:25                     ` Andrei Borzenkov
2021-10-15 21:01                     ` need help in a broken 2TB BTRFS partition Christian Wimmer
2021-10-16 10:08                       ` Qu Wenruo
2021-10-16 17:29                         ` Christian Wimmer
2021-10-16 22:55                           ` Qu Wenruo
2021-10-16 17:35                         ` Christian Wimmer
2021-10-16 23:27                           ` Qu Wenruo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BF92D4FB-0FBF-49F8-A32D-60D56C41AAEC@icloud.com \
    --to=telefonchris@icloud.com \
    --cc=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=wqu@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.