| 1 |
At Sun, 01 Mar 2009 16:27:17 +0200 Nikos Chantziaras <realnc@×××××.de> wrote: |
| 2 |
|
| 3 |
> Allan Gottlieb wrote: |
| 4 |
>> At Sun, 01 Mar 2009 13:57:30 +0200 Nikos Chantziaras <realnc@×××××.de> wrote: |
| 5 |
>> |
| 6 |
>>> Peter Humphrey wrote: |
| 7 |
>>>> As it's Sunday, here's an odd little thing. |
| 8 |
>>>> |
| 9 |
>>>> Not long ago, while booting this machine, four ext3 partitions |
| 10 |
>>>> needed checks on remount count reaching zero. They had been set to |
| 11 |
>>>> 23, 24, 25 and 26 mounts. (I didn't choose the numbers; they were |
| 12 |
>>>> allocated at the time I was creating the file system.) |
| 13 |
>>>> |
| 14 |
>>>> Now, this box does get rebooted, but hardly 23 x 24 x 25 x 26 = |
| 15 |
>>>> 358,800 times all told. At, say, two reboots per day, that would |
| 16 |
>>>> take rather a long time: a little under 500 years if my arithmetic |
| 17 |
>>>> is working. |
| 18 |
>>> I think you're confused. 23 means a check each 23 mounts. With 2 |
| 19 |
>>> mounts per day, that's a check every 12 days for the first and second |
| 20 |
>>> disk. |
| 21 |
>> |
| 22 |
>> I think the point is that 23, 24, 25, 26 are relatively prime so that, |
| 23 |
>> if N is initially zero, it takes 23x24x25x26 increments initially for (N |
| 24 |
>> mod 23), ..., (N mod 26) to all again be zero. |
| 25 |
> |
| 26 |
> Why would it matter if they're all zero or not? |
| 27 |
|
| 28 |
When they are all zero they fsck is triggered. So it was not surprising |
| 29 |
that all the fsck's occurred. What was surprising is that they all |
| 30 |
triggered at the same reboot. |
| 31 |
|
| 32 |
allan |
Archives