Red Hat Bugzilla – Bug 963257
btrfs-zero-log not available in initramfs
Last modified: 2013-06-01 23:01:14 EDT
Description of problem:
If btrfs can't be mounted fedora shows starts a shell to investigate the issue.
The some btrfs tools are available but btrfs-zero-log is missing but sometimes needed, if everything else fails, to solve the issue.
Version-Release number of selected component (if applicable):
btrfs-progs can't control what goes into that environment, I think that's dracut's deal. I don't know what the criteria are for inclusion, but I'll bump the bug over there for discussion.
You can add things in /etc/dracut.conf if you wish, I think.
Ok, kylem tells me maybe we could ship a btrfs.conf for dracut in btrfs-progs. but it seems that for the most part dracut handles this.
dracut folks, what's best?
(In reply to Eric Sandeen from comment #2)
> Ok, kylem tells me maybe we could ship a btrfs.conf for dracut in
> btrfs-progs. but it seems that for the most part dracut handles this.
> dracut folks, what's best?
If you don't introduce a new tool every week, you can just ping me about additional binaries to include in the initramfs for rescue operations.
dracut-027-81.git20130531.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dracut-027-81.git20130531.fc19'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dracut-027-81.git20130531.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.