linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Ming Lei <ming.lei@redhat.com>
Cc: Oleksandr Natalenko <oleksandr@natalenko.name>,
	Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
	linux-block@vger.kernel.org, linux-raid@vger.kernel.org,
	linux-kernel@vger.kernel.org, Shaohua Li <shli@kernel.org>
Subject: Re: I/O hangs after resuming from suspend-to-ram
Date: Thu, 21 Sep 2017 09:30:30 +0200	[thread overview]
Message-ID: <3693727.dykhpN0O6j@merkaba> (raw)
In-Reply-To: <20170920222011.GB5105@ming.t460p>

Ming Lei - 21.09.17, 06:20:
> On Mon, Aug 28, 2017 at 03:10:35PM +0200, Martin Steigerwald wrote:
> > Ming Lei - 28.08.17, 20:58:
> > > On Sun, Aug 27, 2017 at 09:43:52AM +0200, Oleksandr Natalenko wrote:
> > > > Hi.
> > > > 
> > > > Here is disk setup for QEMU VM:
> > > > 
> > > > ===
> > > > [root@archmq ~]# smartctl -i /dev/sda
> > > > …
> > > > Device Model:     QEMU HARDDISK
> > > > Serial Number:    QM00001
> > > > Firmware Version: 2.5+
> > > > User Capacity:    4,294,967,296 bytes [4.29 GB]
> > > > Sector Size:      512 bytes logical/physical
> > > > Device is:        Not in smartctl database [for details use: -P
> > > > showall]
> > > > ATA Version is:   ATA/ATAPI-7, ATA/ATAPI-5 published, ANSI NCITS
> > > > 340-2000
> > > > Local Time is:    Sun Aug 27 09:31:54 2017 CEST
> > > > SMART support is: Available - device has SMART capability.
> > > > SMART support is: Enabled
> > > > 
> > > > [root@archmq ~]# lsblk
> > > > NAME                MAJ:MIN RM  SIZE RO TYPE   MOUNTPOINT
> > > > sda                   8:0    0    4G  0 disk
> > > > `-sda1                8:1    0    4G  0 part
> > > > 
> > > >   `-md0               9:0    0    4G  0 raid10
> > > >   
> > > >     `-system        253:0    0    4G  0 crypt
> > > >     
> > > >       |-system-boot 253:1    0  512M  0 lvm    /boot
> > > >       |-system-swap 253:2    0  512M  0 lvm    [SWAP]
> > > >       
> > > >       `-system-root 253:3    0    3G  0 lvm    /
> > > > 
> > > > sdb                   8:16   0    4G  0 disk
> > > > `-sdb1                8:17   0    4G  0 part
> > > > 
> > > >   `-md0               9:0    0    4G  0 raid10
> > > >   
> > > >     `-system        253:0    0    4G  0 crypt
> > > >     
> > > >       |-system-boot 253:1    0  512M  0 lvm    /boot
> > > >       |-system-swap 253:2    0  512M  0 lvm    [SWAP]
> > > >       
> > > >       `-system-root 253:3    0    3G  0 lvm    /
> > > > 
> > > > sr0                  11:0    1 1024M  0 rom
> > > > 
> > > > [root@archmq ~]# mdadm --misc --detail /dev/md0
> > > > 
> > > > /dev/md0:
> > > >         Version : 1.2
> > > >   
> > > >   Creation Time : Sat Jul 29 16:37:05 2017
> > > >   
> > > >      Raid Level : raid10
> > > >      Array Size : 4191232 (4.00 GiB 4.29 GB)
> > > >   
> > > >   Used Dev Size : 4191232 (4.00 GiB 4.29 GB)
> > > >   
> > > >    Raid Devices : 2
> > > >   
> > > >   Total Devices : 2
> > > >   
> > > >     Persistence : Superblock is persistent
> > > >     
> > > >     Update Time : Sun Aug 27 09:30:33 2017
> > > >     
> > > >           State : clean
> > > >  
> > > >  Active Devices : 2
> > > > 
> > > > Working Devices : 2
> > > > 
> > > >  Failed Devices : 0
> > > >  
> > > >   Spare Devices : 0
> > > >   
> > > >          Layout : far=2
> > > >      
> > > >      Chunk Size : 512K
> > > >      
> > > >            Name : archiso:0
> > > >            UUID : 43f4be59:c8d2fa0a:a94acdff:1c7f2f4e
> > > >          
> > > >          Events : 485
> > > >     
> > > >     Number   Major   Minor   RaidDevice State
> > > >     
> > > >        0       8        1        0      active sync   /dev/sda1
> > > >        1       8       17        1      active sync   /dev/sdb1
> > > > 
> > > > ===
> > > > 
> > > > In words: 2 virtual disks, RAID10 setup with far-2 layout, LUKS on it,
> > > > then
> > > > LVM, then ext4 for boot, swap and btrfs for /.
> > > > 
> > > > I couldn't reproduce the issue with single disk without RAID.
> > > 
> > > Could you verify if the following patch fixes your issue?
> 
> Yes, the patch should address this kind of issue, not related
> with RAID specially, and the latest version can be found in the
> following link:
> 
> 	https://marc.info/?l=linux-block&m=150579298505484&w=2

Thank you.

So if I understand already I can just add

https://github.com/ming1/linux/tree/my_v4.13-safe-scsi-quiesce_V5_for_test

as an remote and go from there.

Thanks,
-- 
Martin

  reply	other threads:[~2017-09-21  7:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 11:45 I/O hangs after resuming from suspend-to-ram Oleksandr Natalenko
2017-08-26 10:37 ` Oleksandr Natalenko
2017-08-26 10:48   ` Oleksandr Natalenko
2017-08-26 11:19     ` Martin Steigerwald
2017-08-26 17:17       ` Wols Lists
2017-08-26 19:33         ` Martin Steigerwald
2017-08-26 13:32     ` Oleksandr Natalenko
2017-08-27  6:02     ` Ming Lei
2017-08-27  7:43       ` Oleksandr Natalenko
2017-08-28 12:58         ` Ming Lei
2017-08-28 13:10           ` Martin Steigerwald
2017-08-28 13:32             ` Ming Lei
2017-09-20 17:25               ` Martin Steigerwald
2017-09-20 22:17                 ` Ming Lei
2017-09-24 17:33                   ` Martin Steigerwald
2017-09-25  2:59                     ` Ming Lei
2017-09-25 14:13                       ` Martin Steigerwald
2017-09-20 22:20             ` Ming Lei
2017-09-21  7:30               ` Martin Steigerwald [this message]
2017-09-21  7:33                 ` Martin Steigerwald
2017-08-28 18:22           ` Oleksandr Natalenko
2017-08-29  0:24             ` Ming Lei
2017-08-29 15:52               ` Oleksandr Natalenko
2017-08-30  2:15                 ` Ming Lei
2017-08-30  5:17                   ` Ming Lei
2017-08-30  6:15                     ` oleksandr
2017-08-30  8:06                       ` Ming Lei
2017-08-30 10:58                         ` oleksandr
2017-08-30 14:37                           ` Ming Lei

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=3693727.dykhpN0O6j@merkaba \
    --to=martin@lichtvoll.de \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=oleksandr@natalenko.name \
    --cc=shli@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).