Thread View: comp.sys.next.sysadmin
2 messages
2 total messages
Started by Jim De Arras
Thu, 01 Oct 1992 02:03
1024 byte sector errors with newfs??
Author: Jim De Arras
Date: Thu, 01 Oct 1992 02:03
Date: Thu, 01 Oct 1992 02:03
100 lines
4851 bytes
4851 bytes
I took eps' advice and did a rebuild of my Wren-8 for 3.0. First, I
reformatted to 1024 bytes sectors. That gained over 50mb, so I felt it was
worth it, even on a 1.4 gb drive. Well, the problem (if it is one) is that
newfs (and BuildDisk) make a table for the fs that generates a warning that the
4096 bytes per inode is not possible, and it will use 4490 bytes per inode.
Not knowing enough about the topic, I just 'feel' that the 4490 bytes per inode
will be a bad fit on a 1024 bytes per sector HD. Here's the newfs report:
cube:11# newfs -N -v /dev/sd0a
/etc/mkfs -N /dev/rsd0a 1455875 46 15 8192 1024 16 10 60 4096 t
Warning: 4096 bytes per inode impossible due
to cylinder group size, using 4490 bytes per inode
Reduce cylinder group size to reduce bytes per inode.
Warning: 25 sector(s) in last cylinder unallocated
/dev/rsd0a: 1455875 sectors in 2110 cylinders of 15 tracks, 46 sectors
1490.8Mb in 132 cyl groups (16 c/g, 11.30Mb/g, 2048 i/g)
super-block backups (for fsck -b#) at:
16, 11104, 22192, 33280, 44368, 55456, 66544, 77632, 88720, 99808,
110896, 121984, 133072, 144160, 155248, 166336, 176656, 187744, 198832,
209920,
221008, 232096, 243184, 254272, 265360, 276448, 287536, 298624, 309712,
320800,
331888, 342976, 353296, 364384, 375472, 386560, 397648, 408736, 419824,
430912,
442000, 453088, 464176, 475264, 486352, 497440, 508528, 519616, 529936,
541024,
552112, 563200, 574288, 585376, 596464, 607552, 618640, 629728, 640816,
651904,
662992, 674080, 685168, 696256, 706576, 717664, 728752, 739840, 750928,
762016,
773104, 784192, 795280, 806368, 817456, 828544, 839632, 850720, 861808,
872896,
883216, 894304, 905392, 916480, 927568, 938656, 949744, 960832, 971920,
983008,
994096, 1005184, 1016272, 1027360, 1038448, 1049536, 1059856, 1070944,
1082032, 1093120,
1104208, 1115296, 1126384, 1137472, 1148560, 1159648, 1170736, 1181824,
1192912, 1204000,
1215088, 1226176, 1236496, 1247584, 1258672, 1269760, 1280848, 1291936,
1303024, 1314112,
1325200, 1336288, 1347376, 1358464, 1369552, 1380640, 1391728, 1402816,
1413136, 1424224,
1435312, 1446400,
I ran it for real with -c 12 to reduce the cyl. group size as requested, and
get:
cube:12# newfs -N -v -c 12 /dev/sd0a
/etc/mkfs -N /dev/rsd0a 1455875 46 15 8192 1024 12 10 60 4096 t
Warning: 25 sector(s) in last cylinder unallocated
/dev/rsd0a: 1455875 sectors in 2110 cylinders of 15 tracks, 46 sectors
1490.8Mb in 176 cyl groups (12 c/g, 8.48Mb/g, 2048 i/g)
super-block backups (for fsck -b#) at:
16, 8344, 16672, 25000, 33328, 41656, 49984, 58312, 66640, 74968,
83296, 91624, 99952, 108280, 116608, 124936, 132496, 140824, 149152, 157480,
165808, 174136, 182464, 190792, 199120, 207448, 215776, 224104, 232432,
240760,
249088, 257416, 264976, 273304, 281632, 289960, 298288, 306616, 314944,
323272,
331600, 339928, 348256, 356584, 364912, 373240, 381568, 389896, 397456,
405784,
414112, 422440, 430768, 439096, 447424, 455752, 464080, 472408, 480736,
489064,
497392, 505720, 514048, 522376, 529936, 538264, 546592, 554920, 563248,
571576,
579904, 588232, 596560, 604888, 613216, 621544, 629872, 638200, 646528,
654856,
662416, 670744, 679072, 687400, 695728, 704056, 712384, 720712, 729040,
737368,
745696, 754024, 762352, 770680, 779008, 787336, 794896, 803224, 811552,
819880,
828208, 836536, 844864, 853192, 861520, 869848, 878176, 886504, 894832,
903160,
911488, 919816, 927376, 935704, 944032, 952360, 960688, 969016, 977344,
985672,
994000, 1002328, 1010656, 1018984, 1027312, 1035640, 1043968, 1052296,
1059856, 1068184,
1076512, 1084840, 1093168, 1101496, 1109824, 1118152, 1126480, 1134808,
1143136, 1151464,
1159792, 1168120, 1176448, 1184776, 1192336, 1200664, 1208992, 1217320,
1225648, 1233976,
1242304, 1250632, 1258960, 1267288, 1275616, 1283944, 1292272, 1300600,
1308928, 1317256,
1324816, 1333144, 1341472, 1349800, 1358128, 1366456, 1374784, 1383112,
1391440, 1399768,
1408096, 1416424, 1424752, 1433080, 1441408, 1449736,
Which looks like a better match to me, but I cannot get either BuildDisk to
'take' this, or can I get the CD/floppy initial build proceedure to use it.
I went ahead and built it as BuildDisk wanted to, and it all seems to work
fine.
Any ideas? Does any of this matter?
Thanks,
Jim
Re: 1024 byte sector errors with newfs??
Author: Eric P. Scott
Date: Sun, 04 Oct 1992 06:16
Date: Sun, 04 Oct 1992 06:16
45 lines
2757 bytes
2757 bytes
In article <1992Oct1.020322.1754@cube.handheld.com> jmd@cube.handheld.com (Jim De Arras) writes: > Well, the problem (if it is one) is that >newfs (and BuildDisk) make a table for the fs that generates a warning that the >4096 bytes per inode is not possible, and it will use 4490 bytes per inode. >Not knowing enough about the topic, I just 'feel' that the 4490 bytes per inode >will be a bad fit on a 1024 bytes per sector HD. bytes per inode has nothing to do with sector size. It's a guess of the average file size on that filesystem. Each filesystem has space for file data, and space for inodes. You need one inode for each file. If you run out of inodes, you can't create any new files. If you have more inodes than you need, you have less space available for file data. You can choose where to draw the line, but it's obviously safer to err on the side of more inodes. How many inodes do you need? That depends on how many files you want to have. For most people, that's directly related to filesystem size. If you have bigger disks, you can have bigger filesystems, and if you have bigger filesystems, you can store more files. Assuming that things scale linearly, the average file size remains more or less constant. So rather than specifying the number of inodes, you're adjusting the inode-to- data ratio. If, for example, you're setting up a filesystem to spool usenet news, you're going to want to tune it for primarily a lot of small files (RTF silliness notwithstanding). If you're going to have a huge swapfile in there, you can reduce the number of inodes, etc. Things are complicated somewhat by cylinder group constraints. In particular, each cylinder group can only hold 2048 inodes. The warning you saw meant that you didn't have enough cylinder groups to supply the number of inodes you requested. By reducing the cylinders/cylinder group ratio, you got more cylinder groups. Optimum values are a function of disk geometry, and thus vary between drive models. If none of this makes any sense to you, check out chapter 7 of _The Design and Implementation of the 4.3BSD UNIX Operating System_ by Leffler, McKusick, Karels, and Quarterman, which has a reasonably detailed explanation of the Berkeley FFS. -=EPS=-
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads