Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1686653 - RFE: provide user output about what was created
Summary: RFE: provide user output about what was created
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: stratis-cli
Version: 8.0
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: 8.0
Assignee: Stratis Team
QA Contact: Jakub Krysl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-07 23:36 UTC by Corey Marthaler
Modified: 2019-03-08 17:30 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Corey Marthaler 2019-03-07 23:36:29 UTC
Description of problem:
Users like to know that their cmd was successful and what/where it was they created.


[root@hayes-01 ~]# stratis fs create my_pool2 my_fs63
[root@hayes-01 ~]# stratis pool create my_pool3 /dev/sdj1
[root@hayes-01 ~]# 



# VDO
[root@hayes-03 ~]# vdo create --writePolicy sync --name my_vdo --device /dev/sde1
Creating VDO my_vdo
Starting VDO my_vdo
Starting compression on VDO my_vdo
VDO instance 178 volume is ready at /dev/mapper/my_vdo

# MKFS
[root@hayes-03 ~]# mkfs /dev/mapper/my_vdo
mke2fs 1.44.3 (10-July-2018)
Discarding device blocks: done                            
Creating filesystem with 115646516 4k blocks and 28917760 inodes
Filesystem UUID: cbc729c3-cdb2-4961-ba8c-5395ed691977
[...]
Writing inode tables: done                            
Writing superblocks and filesystem accounting information: done     


# MD
[root@hayes-03 ~]# mdadm --create /dev/md0 --level=0 --raid-devices=2 /dev/sdb1 /dev/sdc1
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.


# LVM
[root@hayes-03 ~]# pvcreate /dev/sdf1
  Physical volume "/dev/sdf1" successfully created.
[root@hayes-03 ~]# vgcreate VG /dev/sdf1
  Volume group "VG" successfully created
[root@hayes-03 ~]# lvcreate -L 100M VG
  Logical volume "lvol0" created.




Version-Release number of selected component (if applicable):
stratisd-1.0.3-1.el8.x86_64
stratis-cli-1.0.2-1.el8.noarch

Comment 1 mulhern 2019-03-08 16:24:42 UTC
LVM's model is nice and succinct, but xfs.mkfs and vdo are disturbingly chatty,
almost as if the log message are just being piped to stdout. As a user, I would
be made a bit apprehensive by the mkfs.xfs style of communication, until I learned to
ignore it.

Also, this adds the additional bit of adding a --quiet flag for those who are not
interested in having anything printed out, and prefer to assume that if the
command says nothing, it succeeded.

Furthermore, our design is a bit different. I'm not sure about vdo, but mkfs
is _not_ communicating with a daemon over an IPC mechanism.


Note You need to log in before you can comment on or make changes to this bug.