Re: [ceph-users] list admin issues

there is a lot of ceph-users with Gmail accounts, >> perhaps it wouldn't be so bad to actually trying to figure this one out? >> > >> > So can the maintainers of this list please investigate what actually >> gets bounced? Look at my address if you want. >> > I

Re: [ceph-users] Cannot write to cephfs if some osd's are not available on the client network

now this goes against what I thought I learned about ceph fs. You should be able to RW to/from all OSDs, how can it be limited to only a single OSD?? On Sat, Oct 6, 2018 at 4:30 AM Christopher Blum wrote: > I wouldn't recommend you pursuit this any further, but if this is the only > client tha

[ceph-users] mds will not activate

I had to reboot my mds. The hot spare did not kick in and now I am showing the filesystem is degraded and offline. Both mds are showing as up:standby. I am not sure how to proceed. cluster: id: 188c7fba-288f-45e9-bca1-cc5fceccd2a1 health: HEALTH_ERR 1 filesystem is deg

Re: [ceph-users] MDS damaged after mimic 13.2.1 to 13.2.2 upgrade

I'm at scan_links now, will post an update once it has finished. Have you reset the journal after fs recovery as suggested in the doc? quote: If the damaged filesystem contains dirty journal data, it may be recovered next with: cephfs-journal-tool --rank=:0 event recover_dentries list --altern

Re: [ceph-users] list admin issues

Gmail accounts, > perhaps it wouldn't be so bad to actually trying to figure this one out? > > > > So can the maintainers of this list please investigate what actually > gets bounced? Look at my address if you want. > > I got disabled 20181006, 20180927, 201809

Re: [ceph-users] list admin issues

; Christian was on to something, is this intentional? > > Reality is that there is a lot of ceph-users with Gmail accounts, > perhaps it wouldn't be so bad to actually trying to figure this one out? > > > > So can the maintainers of this list please investigate what

Re: [ceph-users] list admin issues

ut? > > So can the maintainers of this list please investigate what actually gets > bounced? Look at my address if you want. > I got disabled 20181006, 20180927, 20180916, 20180725, 20180718 most recently. > Please help! > > Thanks, > Elias > > On Mon, Oct 16, 2017 at 5:41 AM

Re: [ceph-users] list admin issues

ounts, > > > > > perhaps it wouldn't be so bad to actually trying to figure this one > > > > > out? > > > > > > > > > > So can the maintainers of this list please investigate what actually >

Re: [ceph-users] list admin issues

ouldn't be so bad to actually trying to figure this one out? > > > > So can the maintainers of this list please investigate what actually > gets bounced? Look at my address if you want. > > I got disabled 20181006, 20180927, 20180916, 20180725, 20180718 most >

Re: [ceph-users] list admin issues

as on to something, is this intentional? > > Reality is that there is a lot of ceph-users with Gmail accounts, > perhaps it wouldn't be so bad to actually trying to figure this one out? > > > > So can the maintainers of this list please investigate what actually > gets

Re: [ceph-users] list admin issues

iners of this list please investigate what actually gets > bounced? Look at my address if you want. > I got disabled 20181006, 20180927, 20180916, 20180725, 20180718 most recently. > Please help! Same here. -- May the most significant bit of your life be positive. _

Re: [ceph-users] list admin issues

Thanks! Do you have bounce message from google in such case (for example for my account v.tols...@selfip.ru ) сб, 6 окт. 2018 г. в 17:43, Marc Roos : > > Of course it is possible, should be easy to track in log files, looks > like all messages originate from the same host. Let me know what gmail >

Re: [ceph-users] list admin issues

Of course it is possible, should be easy to track in log files, looks like all messages originate from the same host. Let me know what gmail says. Received: from spam1.roosit.eu (spam1.roosit.eu [212.26.193.45]) by sx.f1-outsourcing.eu (Scalix SMTP Relay 11.4.6.13676) via ESMTP; Sat, 06

Re: [ceph-users] list admin issues

сб, 6 окт. 2018 г. в 16:48, Marc Roos : > I have such problems too. And also i have address on gmail (my own domain). I'm asked from list admins to provide bounce message to contact google team. But after three days nobody answered. I don't think that is possible to ask google without message from

Re: [ceph-users] list admin issues

accounts, perhaps > it wouldn't be so bad to actually trying to figure this one out? > > So can the maintainers of this list please investigate what actually gets > bounced? Look at my address if you want. > I got disabled 20181006, 20180927, 20180916, 20180725, 20180718 most > r

Re: [ceph-users] list admin issues

ts, perhaps it wouldn't be so bad to actually trying to figure this one out? So can the maintainers of this list please investigate what actually gets bounced? Look at my address if you want. I got disabled 20181006, 20180927, 20180916, 20180725, 20180718 most recently. Please help! Th

Re: [ceph-users] list admin issues

is one out? > > So can the maintainers of this list please investigate what actually gets > bounced? Look at my address if you want. > I got disabled 20181006, 20180927, 20180916, 20180725, 20180718 most > recently. > Please help! > > Thanks, > Elias > > On Mon,

Re: [ceph-users] list admin issues

his intentional? Reality is that there is a lot of ceph-users with Gmail accounts, perhaps it wouldn't be so bad to actually trying to figure this one out? So can the maintainers of this list please investigate what actually gets bounced? Look at my address if you want. I got disabled 20181006

Re: [ceph-users] Inconsistent directory content in cephfs

Hi, On 05.10.2018 15:33, Sergey Malinin wrote: Are you sure these mounts (work/*06* and work/*6c*) refer to the same directory? On 5.10.2018, at 13:57, Burkhard Linke > wrote: root@host2:~# ls /ceph/sge-tmp/db/work/06/ | wc -l ... r

Re: [ceph-users] Cannot write to cephfs if some osd's are not available on the client network

I wouldn't recommend you pursuit this any further, but if this is the only client that would reside on the same VM as the OSD, one thing you could try is to decrease the primary affinity to 0 [1] for the local OSD . That way that single OSD would never become a primary OSD ;) Disclaimer: This is m