Bug 164256 - [zfs] device entry for volume is not created after zfs receive
Summary: [zfs] device entry for volume is not created after zfs receive
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 9.0-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-17 19:50 UTC by Dmitry Afanasiev
Modified: 2018-01-03 05:15 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry Afanasiev 2012-01-17 19:50:09 UTC 
Device entry for received from snapshot volume must be created, but not created.

How-To-Repeat: # zpool create tank `mdconfig -a -t swap -s 64m`
# zfs create -V 1M tank/vol1
# zfs snapshot tank/vol1@snap
# ls /dev/zvol/tank
vol1            vol1@snap
# zfs send tank/vol1@snap | zfs receive tank/vol2
# ls /dev/zvol/tank
vol1            vol1@snap <- there is no entries for vol2
# zpool export tank
# zpool import tank
# ls /dev/zvol/tank
vol1            vol1@snap       vol2            vol2@snap <- magic!
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2012-01-18 01:05:48 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 2 Dmitry Afanasiev 2012-01-22 15:41:20 UTC 
If pool can't be reimported, below workaround may be used:
zfs clone tank/vol2@snap tank/clone
zfs promote tank/clone
zfs destroy tank/vol2
zfs rename tank/clone tank/vol2
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:58:25 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped