| Summary: | Error message not properly provided when trying to create a volume from a read-only source | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Matt Harris <matthaeus.harris> |
| Component: | logging | Assignee: | krishnan parthasarathi <kparthas> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.1.3 | CC: | gluster-bugs, jdarcy, nsathyan, rahulcs, sac |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | RTP | Mount Type: | --- |
| Documentation: | DP | CRM: | |
| Verified Versions: | master | Category: | --- |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Matt Harris
2011-03-29 18:22:19 UTC
PATCH: http://patches.gluster.com/patch/7059 in master (Detect read-only filesystem and fail the brick creation operation.) PATCH: http://patches.gluster.com/patch/7060 in master (posix: glusterfs.test should be removed xattr immediately after use.) The fix checks if the backend filesystem is read-only and if it supports extended attributes (xattrs). Steps to verify the fix: - Try to create a volume with a read-only filesystem - Try to create a volume with a filesytem that has rw permissions but does not support xattr. You must see appropriate error messages and log of the same. Also check if the xattr trusted.glusterfs.test is *not* present in the backend filesystem, after glusterfsd has started. When the backend is read-only file system, gluster volume create should fail. In this case, # gluster volume create <- succeeds. # gluster volume start <- appears to succeed # gluster volume info Volume Name: test Type: Distribute Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: odin:/mnt/stripe Shows started (but it is not started). mount -t glusterfs <- succeeds (appears to!). # ls /mnt/point ls: cannot access /mnt/point: Transport endpoint is not connected It is only now that we come to know something is wrong and figure out backend file system is read-only and has to be fixed. Is it possible to throw error message during volume create stating read-only file system? Comments above. PATCH: http://patches.gluster.com/patch/7820 in master (Fail volume creation on existing directories of a read-only file system.) The steps to reproduce remain as before. works on master, 2nd & 3rd patch needs to be pushed for 3.1 & 3.2 branches as well. According to Vijay & Avati, not required to back-port the patches. root@Dagobah:~# gluster volume create rovol dagobah:/data/export5/ glusterfs is not supported on brick: dagobah:/data/export5. Setting extended attributes failed, reason: Read-only file system. |