Iyad wrote: > I have two file systems that I need to create a union for. The upperdir > overrides the lowerdir, hence replacing its content. Therefore, > regardless if the upperdir is optional, I do need it in this use case. > > Per the documentation: > > "A read-only overlay of two read-only filesystems may use any > filesystem type." > > I understood that my use case is possible. However, it does contradict > the actual implementation, > > "overlayfs: workdir and upperdir must reside under the same mount" > > and your statement, of course. > > Thanks, > Iyad > > On 04/20/2015 04:01 PM, A. Wan wrote: >> I thought upperdir is now optional but must be read-write if one is >> specified. Therefore if you want the whole stack read-only specify only >> lowdirs and skip the upperdir. Correct me if I am wrong. >> >> Alex When they made upperdir= optional they also changed lowerdir= to allow a (colon separated?) stack of directories. I don't remember if they are stacked from left to right or right to left. I am sure it is in the latest documentation. Alex -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
