Thread (8 messages) 8 messages, 3 authors, 2018-05-13

Re: [PATCH 1/2] bcachefs: On disk data structures

From: Randy Dunlap <hidden>
Date: 2018-05-13 22:49:28
Also in: linux-fsdevel, lkml

On 05/13/2018 03:29 PM, Kent Overstreet wrote:
On Sun, May 13, 2018 at 01:30:06PM -0700, Randy Dunlap wrote:
quoted
On 05/08/2018 03:17 PM, Kent Overstreet wrote:
quoted
quoted
+ * various btrees. There are only a small number of btrees, they're not
+ * sharded - we have one btree for extents, another for inodes, et cetera.
   or shared?
No, I mean sharded - we're e.g. not splitting up the extents btree into one
btree per inode. 
Got it, thanks.
quoted
I know that you have already answered a few comments about endianness,
so maybe you answered this and I missed it.

Can a bcachefs fs be shared, a la NFS?  I.e., can multiple different-endian
clients be accessing the same bcachefs?
NFS works. I haven't tested NFS to different endian clients, wasn't aware there
was any reason to... are there potential issues there I'm not aware of?
Not that I know of.

thanks,
-- 
~Randy
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help