Hello,
we are evaluating Coda here and i have a problem.
I had a server running and two clients actively writing files.
To check crash recovery, i powered down the server. Now the volume
is damaged and SrvLog looks:
12:24:36 Marking as BARREN
12:24:36 Vnode (8000002.48a2.31f5): length incorrect; can't happen!
12:24:36 Marking as BARREN
12:24:36 Vnode 0x8000002.48a4.31f6 incorrect inode - Correcting
12:24:36 f_icreate: bitmap free at 4126, inode 4127 exists!
SrvErr:
could not open key 2 file: No such file or directory
12:24:36 f_icreate: bitmap free at 4126, inode 4127 exists!
Assertion failed: 0, file "/usr/src/debian/coda-5.2.7/coda-src/partition/ftreeifs.c",
line 311
Sleeping forever. You may use gdb to attach to process 1029.root@platin:/vice/s
I had a normal Linux fsck checking the /vicepa partition at bootup,
before starting codasrv.
Is this wrong? I thought the free block bitmaps would go bad without e2fsck.
Are there any other tools to check the coda volume?
regards
Dietmar Goldbeck
--
Alles Gute / best wishes
Dietmar Goldbeck E-Mail: [EMAIL PROTECTED]
Reporter (to Mahatma Gandhi): Mr Gandhi, what do you think of Western
Civilization? Gandhi: I think it would be a good idea.