| Age | Commit message (Collapse) | Author |
|---|
|
ok dcoppa@ otto@
also reviewed by Vadim Zhukov
|
|
Useful for mount_mfs, now you can just say:
# mount_mfs -s 50m swap /tmp
And it will do what you want, taking into account sector size.
Old behaviour of -s (specifying count of sectors) is, of course,
preserved.
All the work was done by Vadim Zhukov (persgray(at)gmail com).
OK myself, otto@, thib@
|
|
|
|
this lets it adapt to large filesystems (disklabel -E automatically increases
fragment and block size for these).
ok otto@
|
|
|
|
ok deraadt
|
|
|
|
gets rid of #include <sys/dkio.h> in sys/ioctl.h and adds #include
<sys/dkio.h> to the places that actually want and use the disk
ioctls.
this became an issue when krw@'s X build failed when he was testing
a change to dkio.h.
tested by krw@
help from and ok miod@
|
|
benefit from planned changes to opendev(3).
ok krw@ marco@
|
|
identifier, allowing the disk to be identified without relying on the
device name.
ok deraadt@ krw@ beck@ marco@ todd@
|
|
we're about to create and warn the user if this is larger than either
physmem or MAXDSIZ; ok deraadt@ krw@ thib@
|
|
|
|
|
|
512-byte blocks. Better than just blowing up. Tweak man page to document
this and clarify various things.
Inspired by problems noted during an install by Harald Dunkel.
Suggestions and man page corrections from otto@ and jmc@
ok beck@
|
|
|
|
512) bytes; ffs is inextricably tied to using b_blkno and disklabel
always uses sectorsize units.
Thus use DEV_BSIZE units for all fields describing ffs filesystems
and convert to/from sectors where required. This enables the creation
and use of ffs filesystems on non-512 byte sectorsize devices.
This diff allows i386 and sgi (the two test platforms) to find
disklabels that are not on a sectorsize boundary. Same change to
further archs coming.
This is a no-op on 512-byte sectorsize devices.
This work triggered by jsing@'s need to create ffs filesystems on
sgi cdroms so we can create cdrom install media for sgi.
sgi testing by jsing@
ok jsing@ pedro@ "looks sane" beck@ weingart@
|
|
deraadt@
|
|
block devs; ok marco@ jmc@ millert@ deraadt@
|
|
either from the disklabel or via -S, is not 512 bytes. Disklabel
partition sizes are sectors and not 512 byte blocks. One less 'block
is 512 bytes' assumption. 2^32 or so to go.
ok otto@ millert@
|
|
|
|
options left of the old tuning list, and it makes sense to have one list
now
- document -T. this was requested by todd (fries), and comes largely from
the description in netbsd's page of the same name
ok millert otto
|
|
here.
ok millert, otto
|
|
-1.
ok henning@ beck@ ray@
|
|
'please fix' jmc
|
|
with and ok jmc@
|
|
|
|
|
|
|
|
a relative path: use realpath to only mount with absolute names.
ok deraadt thib
|
|
|
|
This was not happening since acg.cg_initediblk gets cleared for the
ffs1 case. OK otto@
|
|
won't work yet. There remains sys/ufs work. ok deraadt@
|
|
|
|
|
|
|
|
|
|
|
|
free room in struct partition by packing fragment size and
fragments/block more tighlty and use the resulting space to make
offset and size 48 bits. For the disk part we use spare fields in
struct disklabel. Kernel converts in-mem copy of the on-disk
label if needed, disklabel(8) writes new version.
We are careful to only change fields not used by bootloaders.
Conception of basic scheme by deraadt.
ok deraadt@ krw@
|
|
|
|
recommit the -c changes. For now, we warn only if we cannot honour -c.
ok millert@ deraadt@
|
|
|
|
|
|
changes obviously *MUST* be checked against whatever weird things the
floppies do to fit
|
|
variable name; correct the loop packing more inodes into the cg:
in some cases it could put more fragments into the cg than requested;
give an error if the -c option cannot be honoured. ok millert@ pedro@
|
|
Prevents a core dump found by djm@ when doing mount_mfs -s 80
(yeah, that's a tiny file system); ok millert@ pedro@
|
|
ok otto@
|
|
This was part of the ffs2 changes but was not committed earlier in
order to make the userland and kernel changes independent.
NOTE: the change to newfs require an updated fs.h; building an
updated newfs with the old fs.h may result in a broken filesystem.
OK otto@
|
|
architectures, CGSIZE() was returning something sligthly over one block.
The 'new' fsck would round this value up to a fragment boundary, and end
up trying to access memory beyond allocated space. From mickey@, okay
pedro@, millert@ and otto@.
|
|
produces a bad cg when -c is used. ok pedro@ millert@
|
|
|
