Bug 181766
Summary: | xattrs enabled and can't find / create .reiserfs_priv | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mark Drago <markdrago> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | johnathana, pavel, pfrields, sdl.web, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-16 21:32:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 201088 |
Description
Mark Drago
2006-02-16 12:29:49 UTC
This bug remains in 2.6.15-1.1955_FC5. I get the same messages in /var/log/messages that I received earlier. Is there anything else I can run or information I can provide to make debugging this easier? some of the novell people are looking at fixing reiserfs xattrs upstream, but I'm not sure the state those patches are in (I don't think they're even in -mm yet). *** Bug 182567 has been marked as a duplicate of this bug. *** Fedora core 5 finaly release is less than 3 weeks away. Will this bug get fixed on time? If not I can try to transfer data from reserfs partitions and reformat them as ext3. Dave, In the first comment on bug 182567 [1] you state that this problem can be avoided by disabling selinux. Well, that is what is alluded to when you say to use 'one or the either' of reiser and selinux. Is there a way to selectively disable selinux on certain filesystems. So, I could use selinux on my root partition which is ext3, but disable it on my reiser FS? [1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182567#c1 no, it's a system-wide thing. upstream still hasn't made any real traction on this afaics, so chances are for fc5, it's going to remain broken. A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you. As the reporter of this bug I feel obliged to note that I no longer have any systems using reiserfs and therefore I won't be able to test this bug. It should be noted that to test this bug one just has to verify that SELinux works on a system using reiserfs on one of its partitions. Sorry I couldn't be more help with this one. I switched the partition in question to ext3 exactly because of this bug. Due to the complete lack of interest upstream in making XATTRs work with reiser v3, and Red Hat not providing support for this filesystem in RHEL, I don't see this happening any time soon. I think the answer is going to be that the two are mutually exclusive. |