Page MenuHomeFreeBSD

makefs: add -O (offset) option
ClosedPublic

Authored by guest-svmhdvn on May 17 2017, 9:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 24, 7:39 PM
Unknown Object (File)
Sun, Nov 24, 4:35 PM
Unknown Object (File)
Sat, Nov 23, 12:29 PM
Unknown Object (File)
Fri, Nov 22, 5:42 AM
Unknown Object (File)
Thu, Nov 21, 5:10 PM
Unknown Object (File)
Thu, Nov 21, 5:09 PM
Unknown Object (File)
Thu, Nov 21, 5:09 PM
Unknown Object (File)
Thu, Nov 21, 5:09 PM
Subscribers
None

Details

Summary

submitted by: emaste

ffs.c 1.60
makefs.8 1.44
makefs.c 1.48
makefs.h 1.33
ffs/buf.c 1.20
ffs/mkfs.c 1.27

Obtained from: NetBSD
Relnotes: Yes

Test Plan

Manually tested. Wrote n bytes to a file, provided offset of n, used hexdump to check if original bytes still existed. Will add tests to suite soon.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Seems to be a bug in here:

% makefs -t ffs -O 1024 foo /etc
Calculated size of `foo': 233024 bytes, 423 inodes
Extent size set to 8192
foo: 2.3MB (4752 sectors) block size 8192, fragment size 1024
       using 1 cylinder groups of 2.32MB, 297 blks, 512 inodes.
super-block backups (for fsck -b #) at:
 32,
Populating `foo'
makefs: Writing inode 2 (dir), bytes 0 + 2048: No space left on device

How did you produce this bug? I am not able to reproduce it on my end.

This revision is now accepted and ready to land.May 26 2017, 3:43 PM
This revision was automatically updated to reflect the committed changes.

How did you produce this bug? I am not able to reproduce it on my end.

Indeed, I was not able to reproduce now. I think I may have had other old makefs WIP in the testing tree I used last night.