Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #188918 > unrolled thread
| Started by | Papp Rudolf Péter <peer@peer.hu> |
|---|---|
| First post | 2017-11-12 20:00 +0100 |
| Last post | 2017-11-13 08:20 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.user
where to bugreport a possible filesystem problem Papp Rudolf Péter <peer@peer.hu> - 2017-11-12 20:00 +0100
Re: where to bugreport a possible filesystem problem Sven Hartge <sven@svenhartge.de> - 2017-11-12 20:30 +0100
Re: where to bugreport a possible filesystem problem Papp Rudolf Péter <peer@peer.hu> - 2017-11-13 08:20 +0100
| From | Papp Rudolf Péter <peer@peer.hu> |
|---|---|
| Date | 2017-11-12 20:00 +0100 |
| Subject | where to bugreport a possible filesystem problem |
| Message-ID | <uL5E5-3R1-1@gated-at.bofh.it> |
Dear List! I've a problem with a drbd/ocfs2 dual primary configuration (2 nodes). The problem is if I write a file to the mounted ocfs2 fs then add extended attributes to it after this if I try to read back it is doesn't show any change until read the same file attributes from the other node. After if I go back to the original I get the correct values. But why I need to go to the othet node? root@node01:/# touch /srv/f root@node01:/# setfacl -m g:adm:rwx /srv/f root@node01:/# getfacl /srv/f getfacl: Removing leading '/' from absolute path names # file: srv/f # owner: root # group: root user::rw- group::rwx other::r-- root@node02:~# getfacl /srv/f getfacl: Removing leading '/' from absolute path names # file: srv/f # owner: root # group: root user::rw- group::r-- group:adm:rwx mask::rwx other::r-- root@node01:/# getfacl /srv/f getfacl: Removing leading '/' from absolute path names # file: srv/f # owner: root # group: root user::rw- group::r-- group:adm:rwx mask::rwx other::r-- So could someone please write me where the exact list / bugreport where I can send this question beside this list? Thany you!
[toc] | [next] | [standalone]
| From | Sven Hartge <sven@svenhartge.de> |
|---|---|
| Date | 2017-11-12 20:30 +0100 |
| Message-ID | <uL677-4fB-3@gated-at.bofh.it> |
| In reply to | #188918 |
Papp Rudolf Péter <peer@peer.hu> wrote: > The problem is if I write a file to the mounted ocfs2 fs then add > extended attributes to it after this if I try to read back it is doesn't > show any change until read the same file attributes from the other node. > After if I go back to the original I get the correct values. But why I > need to go to the othet node? > So could someone please write me where the exact list / bugreport > where I can send this question beside this list? Filesystems problems are (in most cases) Kernel problems, so the best package to report this against is the kernel package you are experiencing that problem with. Also: have you tried with a newer kernel, for example from backports? Maybe the problem is fixed there. Then you could add this as an additional data point into your bug report. Grüße, Sven. -- Sigmentation fault. Core dumped.
[toc] | [prev] | [next] | [standalone]
| From | Papp Rudolf Péter <peer@peer.hu> |
|---|---|
| Date | 2017-11-13 08:20 +0100 |
| Message-ID | <uLhce-2WT-3@gated-at.bofh.it> |
| In reply to | #188920 |
I tried with newer kernel from backports as you suggested - also installed the fresh firmware packages too - no change. Weird... Anyway I report back for linux-image package perhaps. Thank you Sven! 2017-11-12 20:19 keltezéssel, Sven Hartge írta: > Papp Rudolf Péter <peer@peer.hu> wrote: > >> The problem is if I write a file to the mounted ocfs2 fs then add >> extended attributes to it after this if I try to read back it is doesn't >> show any change until read the same file attributes from the other node. >> After if I go back to the original I get the correct values. But why I >> need to go to the othet node? >> So could someone please write me where the exact list / bugreport >> where I can send this question beside this list? > Filesystems problems are (in most cases) Kernel problems, so the best > package to report this against is the kernel package you are > experiencing that problem with. > > Also: have you tried with a newer kernel, for example from backports? > Maybe the problem is fixed there. Then you could add this as an > additional data point into your bug report. > > Grüße, > Sven. >
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web