Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1016569

Summary:	btrfs manpage: need btrfs send/receive descriptions in man 8 btrfs
Product:	Red Hat Enterprise Linux 7	Reporter:	Eryu Guan <eguan>
Component:	btrfs-progs	Assignee:	fs-maint
Status:	CLOSED CURRENTRELEASE	QA Contact:	XuWang <xuw>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	eguan, esandeen, fs-maint, lmiksik, pschiffe, wangsl.fnst
Target Milestone:	rc	Keywords:	ManPageChange
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	btrfs-progs-3.14.2-1.el6.x86_64	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-09 11:42:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Eryu Guan 2013-10-08 11:07:18 UTC

Description of problem:
There are no descriptions in man 8 btrfs about send/receive command now. We need them documented.

Version-Release number of selected component (if applicable):
btrfs-progs-0.20.rc1.20130917git194aa4a-1.el7
upstream btrfs-progs too

How reproducible:
always

Steps to Reproduce:
1. man 8 btrfs and search for send/receive command
2.
3.

Actual results:
no description

Expected results:
descriptions about send/receive command

Additional info:

Comment 1 Wang Shilong 2014-03-22 07:24:34 UTC

Version is too old, try btrfs-progsv3.12 or something latest from David' branch

Comment 3 Eric Sandeen 2014-07-14 23:32:35 UTC

See btrfs-receive(8) in the btrfs-progs-v3.14.2

Thanks,
-Eric

Comment 6 XuWang 2014-12-31 03:36:01 UTC

verify with btrfs-progs-3.16.2-1.el7, man btrfs shows following:
BTRFS(8)                       Btrfs Manual                       BTRFS(8)

NAME
       btrfs - control a btrfs filesystem

.....

 send
           Send subvolume data to stdout/file for backup and etc.

           See btrfs-send(8) for details.

       receive
           Receive subvolume data from stdin/file for restore and etc.

           See btrfs-receive(8) for details.

verify with btrfs-progs-3.14.2-2.el6, man btrfs show following:

BTRFS(8)                       Btrfs Manual                       BTRFS(8)

NAME
       btrfs - control a btrfs filesystem

.....

 send
           Send subvolume data to stdout/file for backup and etc.

           See btrfs-send(8) for details.

       receive
           Receive subvolume data from stdin/file for restore and etc.

           See btrfs-receive(8) for details.

So I think the state of this bug can be changed to be verified.