| 1 |
On 04/18/2015 02:31 PM, Paul Colquhoun wrote: |
| 2 |
> On Sat, 18 Apr 2015 11:48:12 walt wrote: |
| 3 |
> |
| 4 |
>> I have two similar but not identical ~amd64 machines, and *one* of |
| 5 |
>> the |
| 6 |
> |
| 7 |
>> two machines is doing something new and strange when I type "mount" |
| 8 |
>> with |
| 9 |
> |
| 10 |
>> no arguments. |
| 11 |
> |
| 12 |
>> |
| 13 |
> |
| 14 |
>> The "bad" machine prints the list of mounted filesystems as it |
| 15 |
>> should, |
| 16 |
> |
| 17 |
>> but then proceeds to read the partition table on every disk in the |
| 18 |
>> machine |
| 19 |
> |
| 20 |
>> and writes a fresh version of /run/blkid/blkid.tab . |
| 21 |
> |
| 22 |
>> |
| 23 |
> |
| 24 |
>> This has the very annoying side effect of spinning up any sleeping |
| 25 |
>> disks, |
| 26 |
> |
| 27 |
>> including the floppy disk (but not the dvd player, thankfully). |
| 28 |
> |
| 29 |
>> |
| 30 |
> |
| 31 |
>> I re-installed util-linux, which installs the "mount" utility, but |
| 32 |
>> no |
| 33 |
> |
| 34 |
>> difference. (The two machines both have util-linux-2.26.1-r1). |
| 35 |
> |
| 36 |
>> |
| 37 |
> |
| 38 |
>> This new behavior began on April 14, FWIW, and the only package I |
| 39 |
>> installed |
| 40 |
> |
| 41 |
>> on that machine that day was gentoo-sources-3.14.38, which is why I |
| 42 |
>> blamed |
| 43 |
> |
| 44 |
>> the new kernel for the new behavior but I discovered since then |
| 45 |
>> that it |
| 46 |
> |
| 47 |
>> happens with all the old kernels too. |
| 48 |
> |
| 49 |
>> |
| 50 |
> |
| 51 |
>> I'm stumped. Any ideas? |
| 52 |
> |
| 53 |
> |
| 54 |
> |
| 55 |
> |
| 56 |
> |
| 57 |
> Are you sure they are both running the same mount command? |
| 58 |
> |
| 59 |
> |
| 60 |
> |
| 61 |
> What does 'type mount' or 'which mount' show for each machine? |
| 62 |
> |
| 63 |
> |
| 64 |
> |
| 65 |
> Is the 'bad' machine perhaps using the '-l' option, which looks like |
| 66 |
> it may need to read information from partitions on the fly: |
| 67 |
> |
| 68 |
> |
| 69 |
> |
| 70 |
> -l, --show-labels |
| 71 |
> |
| 72 |
> Add the labels in the mount output. mount must have permission to |
| 73 |
> read |
| 74 |
> |
| 75 |
> the disk device (e.g. be suid root) for this to work. One can set |
| 76 |
> such |
| 77 |
> |
| 78 |
> a label for ext2, ext3 or ext4 using the e2label(8) utility, or for |
| 79 |
> XFS |
| 80 |
> |
| 81 |
> using xfs_admin(8), or for reiserfs using reiserfstune(8). |
| 82 |
> |
| 83 |
> |
| 84 |
> |
| 85 |
> On the other hand, using '-l' on my machine didn't appear to try |
| 86 |
> anything, and didn't rewrite /run/blkid/blkid.tab but that may be |
| 87 |
> because I don't use labels. |
| 88 |
|
| 89 |
Good questions, thanks. |
| 90 |
|
| 91 |
I know both machines are actually running /bin/mount and not using any |
| 92 |
arguments (like -l) because strace shows me that info in its first line |
| 93 |
of output: |
| 94 |
|
| 95 |
execve("/bin/mount", ["mount"], [/* 61 vars */]) = 0 |
| 96 |
|
| 97 |
That number 61 on the 'bad' machine is 48, though, and I don't know where |
| 98 |
that odd-looking string of characters is generated or what it means. To me |
| 99 |
it looks like a comment in a file of 'c' code. |
| 100 |
|
| 101 |
Still stumped :( |
Archives