[OpenAFS] Resizing an ext2-partition on linux

[ted tcreedon]

Why not use ext3 or reiser?

tedc

-----Original Message-----
From: openafs-info-admin@openafs.org [mailto:openafs-info-admin@openafs.org]
On Behalf Of Kai Moritz
Sent: Saturday, November 18, 2006 1:54 AM
To: openafs-info@openafs.org
Subject: Re: [OpenAFS] Resizing an ext2-partition on linux

Chris Huebsch schrieb:
> Iirc the Admin-Guide says that only for inode-base fileservers (which
> manipulate inode-structures themselves instead of using normal
> file-operations). Name-based fileservers just create normal files an do
> not do any nasty things with inodes. For Linux there is only a
> name-based fileserver available. So you can use all fs-tools of your
> distribution.
>
Good news :)!

But I am a little bit confused. Since installation, I restarted my 
fileserver only once. And olthough it looked like a clean shutdown, 
there were a lot of complaints of the automatic fsck.ext2 at reboot. 
Afterwards the salvager was complaining like this:
-----------------
11/06/2006 10:46:22 STARTING AFS SALVAGER 2.4 (/usr/lib/openafs/salvager)
11/06/2006 10:46:22 Starting salvage of file system partition /vicepa
11/06/2006 10:46:22 SALVAGING FILE SYSTEM PARTITION /vicepa (device=vicepa)
11/06/2006 10:46:23 7 nVolumesInInodeFile 196
11/06/2006 10:46:23 CHECKING CLONED VOLUME 536870916.
11/06/2006 10:46:23 root.afs.readonly (536870916) updated 11/03/2006 16:50
11/06/2006 10:46:23 SALVAGING VOLUME 536870915.
11/06/2006 10:46:23 root.afs (536870915) updated 11/03/2006 16:51
11/06/2006 10:46:23 Vnode 2: version < inode version; fixed (old status)

[...]

11/06/2006 10:46:23 Vnode 338: version < inode version; fixed (old status)
11/06/2006 10:46:23 Vnode 340: version < inode version; fixed (old status)
11/06/2006 10:46:23 Vnode 342: version < inode version; fixed (old status)
11/06/2006 10:46:23 totalInodes 180
11/06/2006 10:46:23 Salvaged root.afs (536870915): 172 files, 179 blocks
11/06/2006 10:46:23 SALVAGING VOLUME 536870927.
11/06/2006 10:46:23 user.ls3.moritz (536870927) updated 11/03/2006 22:55
11/06/2006 10:46:23 Vnode 16: version < inode version; fixed (old status)
11/06/2006 10:46:23 Vnode 76: version < inode version; fixed (old status)

  [...]

11/06/2006 10:46:23 Vnode 5142: version < inode version; fixed (old status)
11/06/2006 10:46:23 Vnode 5142: length incorrect; changed from 0 to 925696
11/06/2006 10:46:23 Vnode 5144: version < inode version; fixed (old status)
11/06/2006 10:46:23 Vnode 5256: version < inode version; fixed (old status)
11/06/2006 10:46:23 totalInodes 1895
11/06/2006 10:46:24 dir vnode 767: special old unlink-while-referenced 
file .__a
fsD04 is deleted (vnode 4984)
11/06/2006 10:46:24 Salvaged user.ls3.moritz (536870927): 1890 files, 
1872274 bl
ocks
11/06/2006 10:46:24 SALVAGING OF PARTITION /vicepa COMPLETED
-------------------------

So I assumed, that the automatic fsck.ext2 messed up something, that the 
salvager had to correct again afterwards.
Perhaps the shutdown was not that clean, like I thought it was. I have 
to check that!

Greetings Kai Moritz
_______________________________________________
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/openafs-info