Re: Message during newfs operation (blocks / cyl group >= 636 in

From: Steven Sim (steven.sim@faplccc.net)
Date: Wed Dec 14 2005 - 18:28:45 EST


Hello ALl;

Thanks for those replying!

Darren Dunham is entirely correct.

Firstly, with regards to the type at newfs (it was indeed newfs
/dev/rdsk/c1t1d0s0 and not newfs /dev/rdsk/c1t1d0s2).

Secondly also on my entirely incorrect interpretation of the message.

Thanks once again. A mistake on my part.

This is a wonderful list.

Warmest Regards
Steven Sim

Darren Dunham wrote:

>># prtvtoc /dev/rdsk/c1t0d0s2 | fmthard -s - /dev/rdsk/c1t1d0s2
>>fmthard: New volume table of contents now in place.
>>
>>So now c1t1d0 has the same VTOC as c1t0d0
>>
>>Then I did a newfs and here's where the msg in question appeared;
>>
>># newfs /dev/rdsk/c1t1d0s2
>>newfs: construct a new file system /dev/rdsk/c1t1d0s0: (y/n)? y
>>
>>
>
>That's very interesting. You asked for slice 2, but it's constructing
>on slice 0? That would be bad. I've never seen that before.
>
>[snip]..
>
>
>>Warning: inode blocks/cyl group (719) >= data blocks (636) in last
>> cylinder group. This implies 10176 sector(s) cannot be allocated
>>
>>
>
>
>
>>Question;
>>
>>Why did newfs not create another cylinder group if the number of blocks
>>in the last cylinder group (719) was greater than the default blocks per
>>cylinder group (636)?
>>
>>
>
>You're reading it backward. There are 636 blocks in the last cylinder
>group. Further, it's 719 inodes per cylinder group, not 719 blocks per
>cylinder group.
>
>
>
>>Should I have instead used an additional -o option in newfs or used
>>mkfs_ufs directly? Perhaps increase cgsize?
>>
>>
>
>You could ignore it, or you could tweak some parameters. Changing the
>size of slice 0 by a cylinder or two would probably eliminate it.
>Otherwise you could change the number of inodes per cylinder up or down
>slightly.
>
>
>
>>Any chance I can recover the 10176 unallocated sectors?
>>
>>
>
>Only by changing the filesystem.
>
>
>

Fujitsu Asia Pte. Ltd.
_____________________________________________________

This e-mail is confidential and may also be privileged. If you are not the intended recipient, please notify us immediately. You should not copy or use it for any purpose, nor disclose its contents to any other person.

Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:37:44 EDT