[ceph-users] Re: cephfs inode backtrace information

2024-04-02 Thread Loïc Tortay
On 29/03/2024 04:18, Niklas Hambüchen wrote: Hi Loïc, I'm surprised by that high storage amount, my "default" pool uses only ~512 Bytes per file, not ~32 KiB like in your pool. That's a 64x difference! (See also my other response to the original post I just sent.) I'm using Ceph 16.2.1. >

[ceph-users] Re: cephfs inode backtrace information

2024-02-01 Thread Loïc Tortay
On 31/01/2024 20:13, Patrick Donnelly wrote: On Tue, Jan 30, 2024 at 5:03 AM Dietmar Rieder wrote: Hello, I have a question regarding the default pool of a cephfs. According to the docs it is recommended to use a fast ssd replicated pool as default pool for cephfs. I'm asking what are the

[ceph-users] Re: cephfs inode backtrace information

2024-01-31 Thread Patrick Donnelly
On Tue, Jan 30, 2024 at 5:03 AM Dietmar Rieder wrote: > > Hello, > > I have a question regarding the default pool of a cephfs. > > According to the docs it is recommended to use a fast ssd replicated > pool as default pool for cephfs. I'm asking what are the space > requirements for storing the

[ceph-users] Re: cephfs inode backtrace information

2024-01-31 Thread Gregory Farnum
The docs recommend a fast SSD pool for the CephFS *metadata*, but the default data pool can be more flexible. The backtraces are relatively small — it's an encoded version of the path an inode is located at, plus the RADOS hobject, which is probably more of the space usage. So it should fit fine