bsdlabel question..
# /dev/da0s1: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 2234 sectors/unit: 35889147 rpm: 15000 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 104857604.2BSD 2048 16384 8 b: 2097152 10485764.2BSD 2048 16384 28552 c: 358891470unused0 0 # raw part, don't edit d: 16777216 31457284.2BSD 2048 16384 28552 e: 8388608 199229444.2BSD 2048 16384 28552 f: 2097152 283115524.2BSD 2048 16384 28552 g: 2097152 304087044.2BSD 2048 16384 28552 h: 3383291 325058564.2BSD 2048 16384 28552 ...This is on a FreeBSD 5.4 machine with a Fuji 15K 18GB scsi drive. Does this disklabel look right? (28553 bps/cpg?) thanks! -- J.D. Bronson Information Services Aurora Health Care - Milwaukee, Wisconsin Office: 414.978.8282 // Fax: 414.314.8787 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel question..
At 05:59 AM 7/30/2005, J.D. Bronson wrote: # /dev/da0s1: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 2234 sectors/unit: 35889147 rpm: 15000 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 104857604.2BSD 2048 16384 8 b: 2097152 10485764.2BSD 2048 16384 28552 c: 358891470unused0 0 # raw part, don't edit d: 16777216 31457284.2BSD 2048 16384 28552 e: 8388608 199229444.2BSD 2048 16384 28552 f: 2097152 283115524.2BSD 2048 16384 28552 g: 2097152 304087044.2BSD 2048 16384 28552 h: 3383291 325058564.2BSD 2048 16384 28552 ...This is on a FreeBSD 5.4 machine with a Fuji 15K 18GB scsi drive. Does this disklabel look right? (28553 bps/cpg?) Yes, it's correct. The number that's liset in the bps/cpg column is not what it appears to be when you create a filesystem using newfs in 5.x. If I recall correctly, it's actually the number of frags in a cyliner group. -Glenn thanks! -- J.D. Bronson Information Services Aurora Health Care - Milwaukee, Wisconsin Office: 414.978.8282 // Fax: 414.314.8787 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel question..
At 05:59 AM 7/30/2005, J.D. Bronson wrote:
# /dev/da0s1:
type: SCSI
disk: da0s1
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 2234
sectors/unit: 35889147
rpm: 15000
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
#size offsetfstype [fsize bsize bps/cpg]
a: 104857604.2BSD 2048 16384 8
b: 2097152 10485764.2BSD 2048 16384 28552
c: 358891470unused0 0 # raw part,
don't edit
d: 16777216 31457284.2BSD 2048 16384 28552
e: 8388608 199229444.2BSD 2048 16384 28552
f: 2097152 283115524.2BSD 2048 16384 28552
g: 2097152 304087044.2BSD 2048 16384 28552
h: 3383291 325058564.2BSD 2048 16384 28552
...This is on a FreeBSD 5.4 machine with a Fuji 15K 18GB scsi drive.
Does this disklabel look right? (28553 bps/cpg?)
I just checked the source for newfs, and my previous reply was
correct. Here's the relevant code that put's that number in the label:
if (pp != NULL) {
pp-p_fstype = FS_BSDFFS;
pp-p_fsize = sblock.fs_fsize;
pp-p_frag = sblock.fs_frag;
pp-p_cpg = sblock.fs_fpg;
}
The last line is the one that inserts that number. sblock.fs_fpg is the
number of frags per cylinder grounp.
-Glenn
thanks!
--
J.D. Bronson
Information Services
Aurora Health Care - Milwaukee, Wisconsin
Office: 414.978.8282 // Fax: 414.314.8787
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel question..
Glenn Dawson [EMAIL PROTECTED] writes: pp-p_fstype = FS_BSDFFS; pp-p_fsize = sblock.fs_fsize; pp-p_frag = sblock.fs_frag; pp-p_cpg = sblock.fs_fpg; } The last line is the one that inserts that number. sblock.fs_fpg is the number of frags per cylinder grounp. Glenn, can you tell me which of those numbers, if any, can be changed after a newfs has been done and the file system well occupied with data? (The lousy sysinstall disk labeler wiped out several of my disk labels and I restored them with zeroes in those fields of the disk label. It worked OK, but I'm guessing it only worked because the bsdlabel defaults were the same as they were when I first did bsdlabel...; newfs If defaults had changed or I used non-default values the first time, I'd have been SOL, right? Or do those values just serve as optimization/tuning values for the kernel?) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel question..
At 02:39 PM 7/30/2005, Gary W. Swearingen wrote: Glenn Dawson [EMAIL PROTECTED] writes: pp-p_fstype = FS_BSDFFS; pp-p_fsize = sblock.fs_fsize; pp-p_frag = sblock.fs_frag; pp-p_cpg = sblock.fs_fpg; } The last line is the one that inserts that number. sblock.fs_fpg is the number of frags per cylinder grounp. Glenn, can you tell me which of those numbers, if any, can be changed after a newfs has been done and the file system well occupied with data? (The lousy sysinstall disk labeler wiped out several of my disk labels and I restored them with zeroes in those fields of the disk label. It worked OK, but I'm guessing it only worked because the bsdlabel defaults were the same as they were when I first did bsdlabel...; newfs If defaults had changed or I used non-default values the first time, I'd have been SOL, right? Or do those values just serve as optimization/tuning values for the kernel?) As far as I am aware, the values listed in the label (see my sample below) for fsize (frag size), bsize (block size) and bps/cpg (used to be cylinders per group in 4.x, but 5.x writes frags per group in that space now) are there only for reference. The numbers that the kernel cares about are the ones in the superblock. # /dev/ad0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 52428804.2BSD 2048 16384 32776 b: 2042752 524288 swap c: 3907168020unused0 0 # raw part, don't edit d: 524288 25670404.2BSD 2048 16384 32776 e: 524288 30913284.2BSD 2048 16384 32776 f: 387101186 36156164.2BSD 2048 16384 28552 Another thing that's interesting to note, is that when you create a file system using newfs from 5.x, it always creates cylinder groups with only one cylinder. That one cylinder has the same amount of blocks as multiple cylinders would have had using older versions of newfs. I'm not really sure why that was done, but it seems to have happened when ufs2 support was added to newfs. I posted to one of the lists a while back to try and find out why, but I never got a response. -Glenn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
