Since last boot, I've got this strange symptom. Filesystem is btrfs. If I list my home dir with dired under emacs I see:
-rwxrwxr-x. 1 nbecker nbecker 207 Dec 3 2015 BACKUP.sh -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history
Attempt to list with ls gives: /usr/bin/ls: cannot access '/home/nbecker/./.bash_history': No such file or directory
I think this means there is a directory entry, but the file doesn't exist? Any suggestion to most reliably repair the damage? I don't care about losing the content of this file.
Can you post dmesg somewhere?
Also output from 'mount | grep -i btrfs'
Chris Murphy
On Mon, Dec 11, 2017, 5:12 AM Neal Becker ndbecker2@gmail.com wrote:
Since last boot, I've got this strange symptom. Filesystem is btrfs. If I list my home dir with dired under emacs I see:
-rwxrwxr-x. 1 nbecker nbecker 207 Dec 3 2015 BACKUP.sh -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_historyAttempt to list with ls gives: /usr/bin/ls: cannot access '/home/nbecker/./.bash_history': No such file or directory
I think this means there is a directory entry, but the file doesn't exist? Any suggestion to most reliably repair the damage? I don't care about losing the content of this file. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Chris Murphy wrote:
Can you post dmesg somewhere?
Also output from 'mount | grep -i btrfs'
Chris Murphy
On Mon, Dec 11, 2017, 5:12 AM Neal Becker ndbecker2@gmail.com wrote:
Since last boot, I've got this strange symptom. Filesystem is btrfs. If I list my home dir with dired under emacs I see:
-rwxrwxr-x. 1 nbecker nbecker 207 Dec 3 2015 BACKUP.sh -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_historyAttempt to list with ls gives: /usr/bin/ls: cannot access '/home/nbecker/./.bash_history': No such file or directory
I think this means there is a directory entry, but the file doesn't exist? Any suggestion to most reliably repair the damage? I don't care about losing the content of this file.
dmesg.txt is here: https://nbecker.fedorapeople.org/dmesg.txt
mount | grep -i btrfs /dev/sda3 on / type btrfs (rw,relatime,seclabel,ssd,space_cache,subvolid=257,subvol=/root) /dev/sda3 on /home type btrfs (rw,relatime,seclabel,ssd,space_cache,subvolid=318,subvol=/home)
I've been using this setup for about 2 years, nothing new.
No Btrfs messages, I think it's unrelated. Seems like a permissions problem.
ls -la /home la -la ~/
And repeat with -Z
Chris Murphy
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.
On Mon, Dec 11, 2017 at 12:11 PM, Neal Becker ndbecker2@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.
On 12/11/17 20:11, Neal Becker wrote:
Since last boot, I've got this strange symptom. Filesystem is btrfs. If I list my home dir with dired under emacs I see:
-rwxrwxr-x. 1 nbecker nbecker 207 Dec 3 2015 BACKUP.sh -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_historyAttempt to list with ls gives: /usr/bin/ls: cannot access '/home/nbecker/./.bash_history': No such file or directory
I think this means there is a directory entry, but the file doesn't exist? Any suggestion to most reliably repair the damage? I don't care about losing the content of this file.
I assume you're executing the commands as yourself. If you "su -" and become root do you see any difference?
OK I see from dmesg that this is kernel 4.14.3, and I've used that quite a bit without problems so I don't think it's related.
What do you get for
$ sudo btrfs dev stats /dev/
If you haven't done a scrub since this problem happened it's worth seeing if that shows any problems:
$ sudo btrfs scrub start / $ sudo btrfs scrub status /
IF there are errors, you can extract those and post them with
$ dmesg | grep -i btrfs
I'll keep looking for this ???? filename business.
Chris Murphy
I had that a long time ago and it was permissions but I do not remember how I solved it but here is a link that talks about it.
https://superuser.com/questions/528459/linux-ls-l-prints-only-question-marks
On Mon, Dec 11, 2017 at 3:23 PM, Chris Murphy lists@colorremedies.com wrote:
OK I see from dmesg that this is kernel 4.14.3, and I've used that quite a bit without problems so I don't think it's related.
What do you get for
$ sudo btrfs dev stats /dev/
If you haven't done a scrub since this problem happened it's worth seeing if that shows any problems:
$ sudo btrfs scrub start / $ sudo btrfs scrub status /
IF there are errors, you can extract those and post them with
$ dmesg | grep -i btrfs
I'll keep looking for this ???? filename business.
Chris Murphy _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
another: https://stackoverflow.com/questions/541533/only-questionmarks-in-linux-dirli...
On Mon, Dec 11, 2017 at 3:28 PM, Néstor rotsen@gmail.com wrote:
I had that a long time ago and it was permissions but I do not remember how I solved it but here is a link that talks about it.
https://superuser.com/questions/528459/linux-ls-l- prints-only-question-marks
On Mon, Dec 11, 2017 at 3:23 PM, Chris Murphy lists@colorremedies.com wrote:
OK I see from dmesg that this is kernel 4.14.3, and I've used that quite a bit without problems so I don't think it's related.
What do you get for
$ sudo btrfs dev stats /dev/
If you haven't done a scrub since this problem happened it's worth seeing if that shows any problems:
$ sudo btrfs scrub start / $ sudo btrfs scrub status /
IF there are errors, you can extract those and post them with
$ dmesg | grep -i btrfs
I'll keep looking for this ???? filename business.
Chris Murphy _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
-- Né§t☼r *Authority gone to one's head is the greatest enemy of Truth*
On Mon, Dec 11, 2017 at 4:29 PM, Néstor rotsen@gmail.com wrote:
another: https://stackoverflow.com/questions/541533/only-questionmarks-in-linux-dirli...
On Mon, Dec 11, 2017 at 3:28 PM, Néstor rotsen@gmail.com wrote:
I had that a long time ago and it was permissions but I do not remember how I solved it but here is a link that talks about it.
https://superuser.com/questions/528459/linux-ls-l-prints-only-question-marks
Yeah this plus running the list commands with sudo should reveal the problem is likely permissions related.
I'm not a fan of stepping on ~/ with chmod -R so I'd try to sort this out directory by directory. There aren't universally correct permissions for everything in ~/
I mucked up my / directory one time. Don't remember what the message(s) were but I had major problems. ls -lZd / should be: dr-xr-xr-x. 20 root root system_u:object_r:root_t:s0 261 Jul 7 21:26 /
Bill
On 12/11/2017 6:28 PM, Néstor wrote:
I had that a long time ago and it was permissions but I do not remember how I solved it but here is a link that talks about it.
https://superuser.com/questions/528459/linux-ls-l-prints-only-question-marks
On Mon, Dec 11, 2017 at 3:23 PM, Chris Murphy <lists@colorremedies.com mailto:lists@colorremedies.com> wrote:
OK I see from dmesg that this is kernel 4.14.3, and I've used that quite a bit without problems so I don't think it's related. What do you get for $ sudo btrfs dev stats /dev/ If you haven't done a scrub since this problem happened it's worth seeing if that shows any problems: $ sudo btrfs scrub start / $ sudo btrfs scrub status / IF there are errors, you can extract those and post them with $ dmesg | grep -i btrfs I'll keep looking for this ???? filename business. Chris Murphy _______________________________________________ users mailing list -- users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org> To unsubscribe send an email to users-leave@lists.fedoraproject.org <mailto:users-leave@lists.fedoraproject.org>-- Né§t☼r /Authority gone to one's head is the greatest enemy of Truth/
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Ed Greshko wrote:
On 12/11/17 20:11, Neal Becker wrote:
Since last boot, I've got this strange symptom. Filesystem is btrfs. If I list my home dir with dired under emacs I see:
-rwxrwxr-x. 1 nbecker nbecker 207 Dec 3 2015 BACKUP.sh -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_historyAttempt to list with ls gives: /usr/bin/ls: cannot access '/home/nbecker/./.bash_history': No such file or directory
I think this means there is a directory entry, but the file doesn't exist? Any suggestion to most reliably repair the damage? I don't care about losing the content of this file.
I assume you're executing the commands as yourself. If you "su -" and become root do you see any difference?
No, same result as root sudo ls -la . [sudo] password for nbecker: ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory total 11548 ... -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history ...
Ran the scrub, no errors found.
This is a simple btrfs of a single partition without raid.
Chris Murphy wrote:
On Mon, Dec 11, 2017 at 12:11 PM, Neal Becker ndbecker2@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.
It's not only the ????, it's this:
sudo ls -lZd /home/nbecker/.bash_history ls: cannot access '/home/nbecker/.bash_history': No such file or directory
That makes me think this can't be a permission issue, but filesystem damage. It persists across reboots also.
I'm not using bcache AFAIK, would that show up in mount options?
/dev/sda3 on /home type btrfs (rw,relatime,seclabel,ssd,space_cache,subvolid=318,subvol=/home)
rpm -q kernel kernel-4.13.16-300.fc27.x86_64 kernel-4.13.16-302.fc27.x86_64 kernel-4.14.3-300.fc27.x86_64
I'm almost sure I saw this first running 4.13.16-302, and it persisted after reboot to 4.14.3-300. I'm only running standard fc27 kernels, nothing homemade.
On 12/12/17 19:58, Neal Becker wrote:
Ed Greshko wrote:
On 12/11/17 20:11, Neal Becker wrote:
Since last boot, I've got this strange symptom. Filesystem is btrfs. If I list my home dir with dired under emacs I see:
-rwxrwxr-x. 1 nbecker nbecker 207 Dec 3 2015 BACKUP.sh -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_historyAttempt to list with ls gives: /usr/bin/ls: cannot access '/home/nbecker/./.bash_history': No such file or directory
I think this means there is a directory entry, but the file doesn't exist? Any suggestion to most reliably repair the damage? I don't care about losing the content of this file.
I assume you're executing the commands as yourself. If you "su -" and become root do you see any difference?
No, same result as root sudo ls -la . [sudo] password for nbecker: ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory total 11548 ... -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history ...
Very odd that it should repeat the message 6 times.....
Not that I'm confident this will be any different but how about disabling selinux temporarily?
sudo setenforce 0 and then try ls?
Ed Greshko wrote:
On 12/12/17 19:58, Neal Becker wrote:
Ed Greshko wrote:
On 12/11/17 20:11, Neal Becker wrote:
Since last boot, I've got this strange symptom. Filesystem is btrfs. If I list my home dir with dired under emacs I see:
-rwxrwxr-x. 1 nbecker nbecker 207 Dec 3 2015 BACKUP.sh -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_historyAttempt to list with ls gives: /usr/bin/ls: cannot access '/home/nbecker/./.bash_history': No such file or directory
I think this means there is a directory entry, but the file doesn't exist? Any suggestion to most reliably repair the damage? I don't care about losing the content of this file.
I assume you're executing the commands as yourself. If you "su -" and become root do you see any difference?
No, same result as root sudo ls -la . [sudo] password for nbecker: ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory ls: cannot access '.bash_history': No such file or directory total 11548 ... -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history -?????????? ? ? ? ? ? .bash_history ...
Very odd that it should repeat the message 6 times.....
Not that I'm confident this will be any different but how about disabling selinux temporarily?
sudo setenforce 0 and then try ls?
BTW, in case it's not clear, only the file ".bash_history" shows an issue.
No difference:
sudo ls -laZ /home/nbecker [...] -rwxrwxr-x. 1 nbecker nbecker unconfined_u:object_r:user_home_t:s0 207 Dec 3 2015 BACKUP.sh -?????????? ? ? ? 0 ? ? .bash_history -?????????? ? ? ? 0 ? ? .bash_history -?????????? ? ? ? 0 ? ? .bash_history -?????????? ? ? ? 0 ? ? .bash_history -?????????? ? ? ? 0 ? ? .bash_history -?????????? ? ? ? 0 ? ? .bash_history -rw-r--r--. 1 nbecker nbecker unconfined_u:object_r:user_home_t:s0 18 Oct 8 2014 .bash_logout [...]
Den 2017-12-12 kl. 13:06, skrev Neal Becker:
rpm -q kernel kernel-4.13.16-300.fc27.x86_64 kernel-4.13.16-302.fc27.x86_64 kernel-4.14.3-300.fc27.x86_64
I'm almost sure I saw this first running 4.13.16-302, and it persisted after reboot to 4.14.3-300. I'm only running standard fc27 kernels, nothing homemade.
Does this problem persist if you boot into kernel-1.13.16-300.fc27.x86_64?
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Jon Ingason wrote:
Den 2017-12-12 kl. 13:06, skrev Neal Becker:
rpm -q kernel kernel-4.13.16-300.fc27.x86_64 kernel-4.13.16-302.fc27.x86_64 kernel-4.14.3-300.fc27.x86_64
I'm almost sure I saw this first running 4.13.16-302, and it persisted after reboot to 4.14.3-300. I'm only running standard fc27 kernels, nothing homemade.
Does this problem persist if you boot into kernel-1.13.16-300.fc27.x86_64?
Didn't test that.
Ran btrfs check --repair booted from a usb stick. Found a few problems and fixed. Probably OK now.
-
Bill Shirley -
Chris Murphy -
Ed Greshko -
Ed Greshko -
Gordon Messmer -
Jon Ingason -
Neal Becker -
Néstor