linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "heming.zhao@suse.com" <heming.zhao@suse.com>
To: David Teigland <teigland@redhat.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Suggestion: lvm2 filters lib needs to show some readable info for end user
Date: Thu, 15 Oct 2020 23:40:32 +0800	[thread overview]
Message-ID: <88157f57-1855-d909-0850-6c6d990628e0@suse.com> (raw)
In-Reply-To: <20201015151634.GA6291@redhat.com>

I just built & ran tag 2.3.10 code, the behavior like before.
(looks it should output: "device has a signature")
```
[tb-clustermd1 ~]# dd if=/dev/zero of=/dev/vdb bs=1M
dd: error writing '/dev/vdb': No space left on device
101+0 records in
100+0 records out
104857600 bytes (105 MB, 100 MiB) copied, 0.0600205 s, 1.7 GB/s
[tb-clustermd1 ~]# dd if=/dev/zero of=/dev/vdc bs=1M
dd: error writing '/dev/vdc': No space left on device
101+0 records in
100+0 records out
104857600 bytes (105 MB, 100 MiB) copied, 0.0566928 s, 1.8 GB/s
[tb-clustermd1 ~]# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
vda    253:0    0   40G  0 disk 
├─vda1 253:1    0    8M  0 part 
├─vda2 253:2    0   38G  0 part /
└─vda3 253:3    0    2G  0 part [SWAP]
vdb    253:16   0  100M  0 disk 
vdc    253:32   0  100M  0 disk 
[tb-clustermd1 ~]# parted -s /dev/vdb mklabel gpt
[tb-clustermd1 ~]# parted -s /dev/vdb mkpart parimary 0% 100%
Warning: The resulting partition is not properly aligned for best performance: 34s % 2048s != 0s
[tb-clustermd1 ~]# mkfs.ext4 /dev/vdb1 
mke2fs 1.45.6 (20-Mar-2020)
Creating filesystem with 102364 1k blocks and 25688 inodes
Filesystem UUID: 56f60edd-a235-460b-b868-3c3d1b5e4e01
Superblock backups stored on blocks: 
        8193, 24577, 40961, 57345, 73729

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done 

[tb-clustermd1 ~]# parted -s /dev/vdb rm 1
[tb-clustermd1 ~]# vgcreate testvg /dev/vdc /dev/vdb
  Device /dev/vdb excluded by a filter.
```


btw, I just built & ran latest master branch code, I saw lots of logs, it looks the code buggy/unstable.
```
# ./tools/lvm vgcreate testvg /dev/vdc /dev/vdb
  Device open /dev/sda already open with di -8193 fd -1
  Device open /dev/vda already open with di -8193 fd -1
  Device open /dev/vda1 already open with di -8193 fd -1
  Device open /dev/vda2 already open with di -8193 fd -1
  Device open /dev/vda3 already open with di -8193 fd -1
  Device open /dev/sdb already open with di -8193 fd -1
  Device open /dev/vdb already open with di -8193 fd -1
  Device open /dev/sdc already open with di -8193 fd -1
  Device open /dev/vdc already open with di -8193 fd -1
  Device open /dev/sdd already open with di -8193 fd -1
  Device open /dev/sde already open with di -8193 fd -1
  Device open /dev/sdf already open with di -8193 fd -1
  Device open /dev/sda already open with di -8193 fd -1
  Device open /dev/vda already open with di -8193 fd -1
  Device open /dev/vda1 already open with di -8193 fd -1
  Device open /dev/vda2 already open with di -8193 fd -1
  Device open /dev/vda3 already open with di -8193 fd -1
  Device open /dev/sdb already open with di -8193 fd -1
  Device open /dev/vdb already open with di -8193 fd -1
  Device open /dev/sdc already open with di -8193 fd -1
  Device open /dev/vdc already open with di -8193 fd -1
  Device open /dev/sdd already open with di -8193 fd -1
  Device open /dev/sde already open with di -8193 fd -1
  Device open /dev/sdf already open with di -8193 fd -1
  Device open /dev/vdc already open with di -8193 fd -1
  Device open /dev/vdc already open with di -8193 fd -1
  Device open /dev/vdb already open with di -8193 fd -1
  Device open /dev/vdb already open with di -8193 fd -1
  Device open /dev/vdc already open with di -8193 fd -1
  Device open /dev/vdb already open with di -8193 fd -1
  Device open /dev/vdc already open with di -8193 fd -1
  Device open /dev/vdb already open with di -8193 fd -1
```

On 10/15/20 11:16 PM, David Teigland wrote:
> On Thu, Oct 15, 2020 at 11:05:38PM +0800, heming.zhao@suse.com wrote:
>> Hello David,
>>
>> I don't know why I could use "git show 1fa48ba9d60ad34c5957b80024ef660ffb11161f" to
>> see your patch, but I can't find the commit in "git log" output (in master branch).
>> And the related code also doesn't be changed in master branch.
> 
> See these commits in the master branch:
> 450f272b31ef95bd7cb61812d9ef0525c7c1c341
> 74ed6e8a9969bb7d20c21f88b53e6134d81eab1d
> 0143c7aebe2389ceada6ca0a314a3ff0fd9cdfef
> 
> (The link I sent previously wasn't merged.)
> 

      reply	other threads:[~2020-10-15 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 11:02 [linux-lvm] Suggestion: lvm2 filters lib needs to show some readable info for end user heming.zhao
2020-07-20 17:54 ` David Teigland
2020-07-21  8:37   ` heming.zhao
2020-10-15 15:05   ` heming.zhao
2020-10-15 15:16     ` David Teigland
2020-10-15 15:40       ` heming.zhao [this message]

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=88157f57-1855-d909-0850-6c6d990628e0@suse.com \
    --to=heming.zhao@suse.com \
    --cc=linux-lvm@redhat.com \
    --cc=teigland@redhat.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 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).