| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Am 01.11.2010 14:13, schrieb Alan McKinnon: |
| 5 |
> Apparently, though unproven, at 14:51 on Monday 01 November 2010, Harry Putnam |
| 6 |
> did opine thusly: |
| 7 |
> |
| 8 |
>> Alan McKinnon <alan.mckinnon@×××××.com> writes: |
| 9 |
>> |
| 10 |
>> |
| 11 |
>> [...] |
| 12 |
>> |
| 13 |
>>>>> What shell are you using? |
| 14 |
>>>>> What is the output of "echo $HOME"? |
| 15 |
>>>> |
| 16 |
>>>> My shell is xterm... and was just updated to: |
| 17 |
>>>> Wed Oct 27 10:15:06 2010 >>> x11-terms/xterm-262 |
| 18 |
>>> |
| 19 |
>>> That's the terminal. |
| 20 |
>>> |
| 21 |
>>> What shell do you use/ |
| 22 |
>> |
| 23 |
>> Sorry... still asleep... bash-4.1_p9 |
| 24 |
>> |
| 25 |
>> |
| 26 |
>> Willie Wong <wwong@××××××××××××××.EDU> writes: |
| 27 |
>> |
| 28 |
>> [...] |
| 29 |
>> |
| 30 |
>>> Before we go further, when you said `ls' will not complete against |
| 31 |
>>> $HOME, which of the following scenario did you mean? |
| 32 |
>>> |
| 33 |
>>> a) you typed `ls $HOME' as a user (the one I think Alan thinks you |
| 34 |
>>> |
| 35 |
>>> mean) |
| 36 |
>>> |
| 37 |
>>> b) you type `ls' while in your home directory (/home/reader) |
| 38 |
>>> c) you typed `ls /home/reader' ? |
| 39 |
>> |
| 40 |
>> All three of those produce the same effect. Also if run from root |
| 41 |
>> shell against my users home `# ls /home/reader' |
| 42 |
>> |
| 43 |
>> The command just hangs there as described. |
| 44 |
>> |
| 45 |
>> However, as indicated earlier... my user or root can run `ls' against |
| 46 |
>> any other directory like normal. |
| 47 |
>> |
| 48 |
>> ls /etc |
| 49 |
>> |
| 50 |
>> Shows the content of /etc |
| 51 |
>> |
| 52 |
>> ls /home/reader |
| 53 |
>> |
| 54 |
>> Hangs eternally. |
| 55 |
>> |
| 56 |
>> Also, as mentioned, I can view /home/reader with emacs in dired |
| 57 |
>> (directory) mode, Which oddly enough uses ls and ls switches for that |
| 58 |
>> display far as I know. |
| 59 |
>> |
| 60 |
>> However, vim will not display /home/reader... and |
| 61 |
>> hangs eternally... requiring the shell to be killed. |
| 62 |
>> |
| 63 |
>> Viewing $HOME with emacs shows nothing untoward that I see. I thought |
| 64 |
>> maybe I'd somehow acquired thousands of files and `ls' was just taking |
| 65 |
>> forever to display the list... but no... nothing unusual in $HOME. |
| 66 |
> |
| 67 |
> |
| 68 |
> I suspect directory corruption in /home - is it a separate partition? |
| 69 |
> |
| 70 |
> I don't recall if you mentioned this or not, do you get the same result if you |
| 71 |
> run "ls $HOME" as root? root's home dir is not on /home so that will vbe a |
| 72 |
> valuable clue. If that command works, do an fsck on /home |
| 73 |
> |
| 74 |
> |
| 75 |
Could also some problem with the inodes, could't? |
| 76 |
-----BEGIN PGP SIGNATURE----- |
| 77 |
Version: GnuPG v2.0.14 (MingW32) |
| 78 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 79 |
|
| 80 |
iQEcBAEBAgAGBQJMzsDmAAoJEB8n+SuWCkjvtl0H/3Ex2l3razqJiXXV8BTUJSt6 |
| 81 |
6IxjvQ12e48vj6ED8vJ083LEEotGswTTzODHHdJApGoSgp8msCodSyjudscLNJRJ |
| 82 |
8cpdGWOsIV8paLUfSkDXZConLdpfJp1fgTiupGrkXdCfW2jKM1R2K1dC7uPr+wXf |
| 83 |
nZtgaXGBw7Ao04mlgPNgXYXlN2V9JsWelc1AJhWBoCocopJj/eEeaHSCrLFzhInF |
| 84 |
Sm5GjVRaIEGKbplzi5mBgOgvQ756nCeAzjXM/Va5obvIrwbnGNd9VEJQ+WnJGCKT |
| 85 |
lFcfmRGorPPPYktvQTM3BiZf6Fs23C0ude+lZBgt4I+HtCyKrYHANLFrx1WBC3s= |
| 86 |
=IKBq |
| 87 |
-----END PGP SIGNATURE----- |
Archives