On Mon, Dec 11, 2017 at 12:11 PM, Neal Becker <ndbecker2(a)gmail.com> wrote:
Chris Murphy wrote:
> No Btrfs messages, I think it's unrelated. Seems like a permissions
> problem.
>
> ls -la /home
> la -la ~/
>
> And repeat with -Z
>
>
> Chris Murphy
ls -la ~/
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
total 11532
drwxr-xr-x. 1 nbecker nbecker 5808 Dec 11 13:22 .
drwxr-xr-x. 1 root root 48 Aug 2 19:32 ..
...
-?????????? ? ? ? ? ? .bash_history
-?????????? ? ? ? ? ? .bash_history
-?????????? ? ? ? ? ? .bash_history
-?????????? ? ? ? ? ? .bash_history
-?????????? ? ? ? ? ? .bash_history
-?????????? ? ? ? ? ? .bash_history
-rw-r--r--. 1 nbecker nbecker 18 Oct 8 2014 .bash_logout
...
Are you sure? Doesn't look like a permission problem to me.
I'm not sure, that's why I asked for ls -Z as well for both /home and
for ~/ which are different things. But you're right, something's off.
Was there a recent kernel update applied? Are you using bcache? There
is a block layer bug in 4.14.0 and 4.14.1, fixed in 4.14.2 that can
cause a lot of file system damage when bcache is used.
Somewhere I saw this ???? filename thing come up, somewhat recently,
but I can't find it so far.
--
Chris Murphy