All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	"linux-unionfs@vger.kernel.org" <linux-unionfs@vger.kernel.org>
Subject: Re: Overlayfs reverse mapping
Date: Sat, 22 Apr 2017 04:34:47 +0900	[thread overview]
Message-ID: <7402.1492803287@jrobl> (raw)
In-Reply-To: <CAOQ4uxiBKku_jh8bbCvB1L9TytdcqDUuJSnjCREsc+nacYngtw@mail.gmail.com>

Amir Goldstein:
> That would be names of files reserved for use by fs that user
> cannot use (i.e. .wh. files). Miklos did not  mean that aufs handles
> lost+found, but that it lives without a problem with reserved filenames.

Ah, reserving a filename prefix ".wh.". I see.
Thanx for the explanation.

By the way, putting extra things under lost+found is not a good idea I
think.
Have you ever tried restoring files manually from lost+found?
When an administrator meets such case, he will digging lost+found and
copy the files one by one with guessing the filenames. If he is not sure
what the file is, then he may leave it under lost+found.
For such case, the entries related to overlayfs will be left, and the
administrator will spend some sleepless nights with thinking "What are
these files? How can I restore them?"


J. R. Okajima

  reply	other threads:[~2017-04-21 19:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 11:34 Overlayfs reverse mapping Amir Goldstein
2017-04-19 13:15 ` Miklos Szeredi
2017-04-20  9:22   ` Amir Goldstein
2017-04-21 13:24     ` Miklos Szeredi
2017-04-21 18:44       ` J. R. Okajima
2017-04-21 19:04         ` Amir Goldstein
2017-04-21 19:34           ` J. R. Okajima [this message]
2017-04-21 19:42             ` Amir Goldstein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7402.1492803287@jrobl \
    --to=hooanon05g@gmail.com \
    --cc=amir73il@gmail.com \
    --cc=linux-unionfs@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.