Hello OmegaPhil,
OmegaPhil:
> Reading the manpage, I think this is covered with:
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> The whiteout prefix (.wh.) is reserved on all branches. Users
> should not handle the filename
> begins with this prefix. In order to future whiteout, the
> maximum filename length is limited
> by the longest value - 4 * 2 - 1 - 4 =3D 242. It means you
> cannot handle such long name in
> aufs, even if it surely exists on the underlying branch fs. The
> readdir(3)/getdents(2) call
> show you such name, but the d_type is set to DT_UNKNOWN. It may
> be a violation of POSIX.
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> 246 is pretty close to the extfs/btrfs max of 255B, so I doubt its going
> to get 'solved' any time soon.
I am glad that you already referred aufs manual.
If you read include/uapi/linux/aufs_type.h, you would find this macro
too.
/* a limit for rmdir/rename a dir and copyup */
#define AUFS_MAX_NAMELEN (NAME_MAX \
- AUFS_WH_PFX_LEN * 2 /* doubly whiteouted */\
- 1 /* dot */\
- AUFS_WH_TMP_LEN) /* hex */
NAME_MAX is defined as 255 which comes from POSIX.
Obviously your 246 is longer than aufs' 242 limit, and aufs reports the
error expectedly.
J. R. Okajima
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
