| 1 |
On Mon, 2004-03-08 at 21:06, Mark Knecht wrote: |
| 2 |
> > !!! ERROR: There appears to be FILE SYSTEM CORRUPTION. A file that |
| 3 |
> > is listed |
| 4 |
> |
| 5 |
> This is a known bug with hashed btrees in the ext3 filesystem. It's |
| 6 |
> been around a while. Don't know why it isn;t getting fices unless the |
| 7 |
> fix is difficult. |
| 8 |
|
| 9 |
This has got to be the worst error message I've seen in some time. It |
| 10 |
is basically a panic inducer where there is no need for one. |
| 11 |
|
| 12 |
I have a question for those who know a thing or two about filesystems |
| 13 |
(which I do not count myself amongst). I have a server that I won't |
| 14 |
have physical access to for at least a few weeks. Unmounting /var and |
| 15 |
tune2fsing as recommended in the bug report would be a major pain and I |
| 16 |
would like to wait until I have physical access to the box just in |
| 17 |
case. |
| 18 |
|
| 19 |
Is this something that can cause cascading problems or can I put it off |
| 20 |
for a few weeks? (So far the box has been functioning perfectly.) Any |
| 21 |
thoughts / advice would be appreciated. |
| 22 |
|
| 23 |
-Collin |
| 24 |
|
| 25 |
P.S. I asked the same question of the bug responders on Bugzilla but |
| 26 |
so far have gotten nada. |
| 27 |
|
| 28 |
-- |
| 29 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 30 |
Collin Starkweather, Ph.D. collin.starkweather@××××××××××××××××××.com |
| 31 |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
Archives