[OpenAFS] Max number of files in volume?
Hamie
hamish@travellingkiwi.com
Mon, 17 May 2004 12:41:37 +0100
Horst Birthelmer wrote:
>
> On Monday, May 17, 2004, at 12:04 PM, Hamie wrote:
>
>> Horst Birthelmer wrote:
>>
>>>
>>> On Thursday, May 13, 2004, at 01:48 PM, Hamie wrote:
>>>
>>>> Tino Schwarze wrote:
>>>>
>>>>> On Thu, May 13, 2004 at 11:59:04AM +0100, Hamie wrote:
>>>>>
>>>>>
>>>>>>> Just a thought ... Is your partition full??
>>>>>>>
>>>>>> No... 92%, but it's a 16GB filesystem (JFS on AIX 5.1).
>>>>>>
>>>>>>
>>>>>> I did find this little bit of trouble though...
>>>>>>
>>>>>> r01ai01:/usr/afs/logs# bos salvage intl-mgw01.baplc.com
>>>>>> -partition /vicepa -localauth
>>>>>> bos: shutting down fs.
>>>>>> Starting salvage.
>>>>>> bos: waiting for salvage to complete.
>>>>>> bos: salvage completed
>>>>>> bos: restarting fs.
>>>>>> br01ai01:/usr/afs/logs# ls
>>>>>> br01ai01:/usr/afs/logs# cat SalvageLog
>>>>>> @(#)Base configuration afs3.6 2.45
>>>>>> 05/13/2004 11:54:40 STARTING AFS SALVAGER 2.4
>>>>>> (/usr/afs/bin/salvager -f /vicepa)
>>>>>> 05/13/2004 11:54:40 Unable to read block 1, partition
>>>>>> 05/13/2004 11:54:40 Unable to read superblock on /proc.
>>>>>> 05/13/2004 11:54:40 SALVAGING FILE SYSTEM PARTITION /vicepa
>>>>>> (device=vicepa)
>>>>>> 05/13/2004 11:54:40 ***Forced salvage of all volumes on this
>>>>>> partition***
>>>>>> 05/13/2004 11:54:49 File system /dev/rvicepa is in a bad state.
>>>>>> 05/13/2004 11:54:49 Call your IBM representative.
>>>>>> Unable to get inodes for "vicepa"; not salvaged
>>>>>>
>>>>>
>>>>> I don't know anything about JFS, but is it possible that the
>>>>> partition
>>>>> is out of inodes?
>>>>>
>>>>>
>>>>
>>>> unfortunately (?) not..
>>>>
>>>> /dev/vicepa 15597568 1302472 92% 270 1% /vicepa
>>>> /dev/vicepb 15597568 15066904 4% 587 1% /vicepb
>>>>
>>>> Only 1% inodes used...
>>>>
>>> Is this a namei fileserver??
>>> If yes, try to enter /vicepa and do something in the directory.
>>> Copy some files or ... whatever just for making shure your
>>> filesystem is accessible.
>>>
>>
>> The answer was sort of... AFS could read & write happily to existing
>> volumes... But the filesystem appeared to be hosed somewhere between
>> the JFS itself & the disk...
>>
>> Probably due to a power outage last week on the ESS that holds the
>> actual disk. I had to fsck the filesystems (/vicepa & /vicepb) before
>> they'd mount, and I'm running a salvage now, but it looks like it's
>> come back. Very strange, because it was only the JFS filesystems on
>> that volumegroup that were affected. The jfs2 filesystems were
>> fine... There are a whole lot (9) of empty volume files in the
>> /vicepa filesystem though... They look like they're from attempts to
>> move volumes late last week...
>>
>
> What do you actually mean by "empty volume files" ??
>
.vl files with 0 length... The salvage removed them. Here's the log. It
was creating new ones everytime I tried to move a volume... This
paritition only had the one... It all seems to be working now.
05/17/2004 11:05:54 STARTING AFS SALVAGER 2.4 (/usr/afs/bin/salvager -f
/vicepb)
05/17/2004 11:05:54 Unable to read block 1, partition
05/17/2004 11:05:54 Unable to read superblock on /proc.
05/17/2004 11:05:54 SALVAGING FILE SYSTEM PARTITION /vicepb (device=vicepb)
05/17/2004 11:05:54 ***Forced salvage of all volumes on this partition***
05/17/2004 11:08:18 /vicepb/V0536871182.vl is not a legitimate volume
header file; deleted
05/17/2004 11:08:18 SALVAGING VOLUME 536871078.
05/17/2004 11:08:18 mail.qu.spam (536871078) updated 05/17/2004 11:05
05/17/2004 11:08:18 Vnode 864 (unique 238232): corresponding inode 4272
is missing; vnode deleted, vnode mod time=Sun May 16 19:09:47 2004
05/17/2004 11:08:18 Vnode 866 (unique 238233): corresponding inode 4273
is missing; vnode deleted, vnode mod time=Sun May 16 19:11:38 2004
05/17/2004 11:08:18 Vnode 868 (unique 238234): corresponding inode 4274
is missing; vnode deleted, vnode mod time=Sun May 16 19:15:35 2004
05/17/2004 11:08:18 Vnode 870 (unique 238235): corresponding inode 4275
is missing; vnode deleted, vnode mod time=Sun May 16 19:19:38 2004
05/17/2004 11:08:18 Vnode 872 (unique 238236): corresponding inode 4276
is missing; vnode deleted, vnode mod time=Sun May 16 19:20:08 2004
05/17/2004 11:08:18 Vnode 874 (unique 238237): corresponding inode 4277
is missing; vnode deleted, vnode mod time=Sun May 16 19:21:47 2004
05/17/2004 11:08:18 Vnode 876 (unique 238238): corresponding inode 4278
is missing; vnode deleted, vnode mod time=Sun May 16 19:23:06 2004
05/17/2004 11:08:18 Vnode 878 (unique 238239): corresponding inode 4279
is missing; vnode deleted, vnode mod time=Sun May 16 19:25:37 2004
05/17/2004 11:08:18 Vnode 880 (unique 238240): corresponding inode 4280
is missing; vnode deleted, vnode mod time=Sun May 16 19:27:00 2004
05/17/2004 11:08:18 Vnode 882 (unique 238241): corresponding inode 4281
is missing; vnode deleted, vnode mod time=Sun May 16 19:27:26 2004
05/17/2004 11:08:18 Vnode 884 (unique 238242): corresponding inode 4282
is missing; vnode deleted, vnode mod time=Sun May 16 19:28:52 2004
05/17/2004 11:08:18 Vnode 886 (unique 238243): corresponding inode 4283
is missing; vnode deleted, vnode mod time=Sun May 16 19:29:46 2004
05/17/2004 11:08:18 Vnode 888 (unique 238244): corresponding inode 4284
is missing; vnode deleted, vnode mod time=Sun May 16 19:29:47 2004
05/17/2004 11:08:18 Vnode 890 (unique 238245): corresponding inode 4285
is missing; vnode deleted, vnode mod time=Sun May 16 19:30:48 2004
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-d4ce83a63a21660d9215c95b9a3519aa-20040516-191535-5783638-03-93.gz
has no inode (vnode 868, unique 238234) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-b055cf68935a56575942c713c9f85bc7-20040516-192146-1376374-41-22.gz
has no inode (vnode 874, unique 238237) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-32b30693d9a581182fb7fbecc75dd738-20040516-192700-835640-01-70.gz
has no inode (vnode 880, unique 238240) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-88bd5f8b162ff4ab6d8895ec52ab1895-20040516-192305-5464176-01-17.gz
has no inode (vnode 876, unique 238238) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-09a043a6e8ea02c5386908b7ec7ec77e-20040516-192946-1376374-41-35.gz
has no inode (vnode 886, unique 238243) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-d4ed7246fd1aa50a42064c6778c5253c-20040516-193048-5709992-22-84.gz
has no inode (vnode 890, unique 238245) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-17bc5169ceaeaf942ed685edd97395f7-20040516-192537-835640-01-67.gz
has no inode (vnode 878, unique 238239) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-a12b5c0eb096b8aa2542a29f088244c0-20040516-192008-5390432-28-91.gz
has no inode (vnode 872, unique 238236) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-65a7959bcd641c0711375d1dbdd2ef0e-20040516-191938-1376374-41-16.gz
has no inode (vnode 870, unique 238235) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-69f11f4fa51c75d3288d3e3fc9dbb1f4-20040516-192947-2736190-20-78.gz
has no inode (vnode 888, unique 238244) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-cac258d68841e0a0f57b97437845734a-20040516-192851-5464176-01-26.gz
has no inode (vnode 884, unique 238242) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-c269ae77d031ca2bf3f6d254cc46e5f2-20040516-192726-5709992-22-78.gz
has no inode (vnode 882, unique 238241) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-fa319aac939e4de6c60d644855566383-20040516-191138-5709992-22-45.gz
has no inode (vnode 866, unique 238233) -- deleted
05/17/2004 11:08:18 dir vnode 1: invalid entry:
./spam-7be7843d24a9f1b3fe0be7b40be1b464-20040516-190947-2441400-02-4.gz
has no inode (vnode 864, unique 238232) -- deleted
05/17/2004 11:08:18 Salvaged mail.qu.spam (536871078): 1355 files, 5393
blocks
05/17/2004 11:08:18 SALVAGING VOLUME 536871161.
05/17/2004 11:08:18 reflector.logs (536871161) updated 05/17/2004 10:04
05/17/2004 11:08:18 Vnode 2: length incorrect; changed from 5588240 to
4047232
05/17/2004 11:08:18 Vnode 4: length incorrect; changed from 6002963 to
4348464
05/17/2004 11:08:18 Vnode 6: length incorrect; changed from 5589808 to
4048464
05/17/2004 11:08:18 Vnode 8: length incorrect; changed from 6004467 to
4350402
05/17/2004 11:08:18 Vnode 10: length incorrect; changed from 5589136 to
4048464
05/17/2004 11:08:18 Vnode 12: length incorrect; changed from 6003883 to
4349555
05/17/2004 11:08:18 Vnode 14: length incorrect; changed from 5591712 to
4051936
05/17/2004 11:08:18 Vnode 16: length incorrect; changed from 6007273 to
4352728
05/17/2004 11:08:18 Salvaged reflector.logs (536871161): 9 files, 32815
blocks
05/17/2004 11:08:18 SALVAGING OF PARTITION /vicepb COMPLETED
> In a namei fileserver the *.vol files in the root directory of the
> partition (vicep*) don't contain any 'real' data from the volume.
>
yeah. They are just the volume headers aren't they IIRC...
> Horst
>