#
4179ce18 |
| 26-Feb-2010 |
Kirk McKusick <mckusick@FreeBSD.org> |
MFC of 203763, 203764, 203768, 203769, 203770, 203782, and 203784.
These fixes correct a problem in the file system that treats large inode numbers as negative rather than unsigned. For a default (1
MFC of 203763, 203764, 203768, 203769, 203770, 203782, and 203784.
These fixes correct a problem in the file system that treats large inode numbers as negative rather than unsigned. For a default (16K block) file system, this bug began to show up at a file system size above about 16Tb.
These fixes also update newfs to ensure that it will never create a filesystem with more than 2^32 inodes.
They also update libufs, tunefs, and growfs so that they properly handle inode numbers as unsigned.
Reported by: Scott Burns, John Kilburg, and Bruce Evans Followup by: Jeff Roberson PR: 133980
show more ...
|
#
81479e68 |
| 11-Feb-2010 |
Kirk McKusick <mckusick@FreeBSD.org> |
One last pass to get all the unsigned comparisons correct.
|
#
cb464c69 |
| 10-Feb-2010 |
Kirk McKusick <mckusick@FreeBSD.org> |
Ensure that newfs will never create a filesystem with more than 2^32 inodes by cutting back on the number of inodes per cylinder group if necessary to stay under the limit. For a default (16K block)
Ensure that newfs will never create a filesystem with more than 2^32 inodes by cutting back on the number of inodes per cylinder group if necessary to stay under the limit. For a default (16K block) file system, this limit begins to take effect for file systems above 32Tb.
This fix is in addition to -r203763 which corrected a problem in the kernel that treated large inode numbers as negative rather than unsigned. For a default (16K block) file system, this bug began to show up at a file system size above about 16Tb.
Reported by: Scott Burns, John Kilburg, Bruce Evans Followup by: Jeff Roberson PR: 133980 MFC after: 2 weeks
show more ...
|
#
9199c09a |
| 06-Jan-2010 |
Warner Losh <imp@FreeBSD.org> |
Merge from head at r201628.
# This hasn't been tested, and there are at least three bad commits # that need to be backed out before the branch will be stable again.
|
#
1457e0cd |
| 02-Jan-2010 |
Martin Blapp <mbr@FreeBSD.org> |
Fix typo: s/partion/partition/
Submitted by: Marc Balmer <marc@msys.ch> MFC after: 3 days
|
Revision tags: release/8.0.0_cvs, release/8.0.0 |
|
#
7d4b968b |
| 17-Sep-2009 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Merge from head up to r188941 (last revision before the USB stack switch)
|
Revision tags: release/7.2.0_cvs, release/7.2.0 |
|
#
1829d5da |
| 12-Mar-2009 |
Warner Losh <imp@FreeBSD.org> |
Update the projects tree to a newer FreeBSD current.
|
#
02dda286 |
| 12-Feb-2009 |
Olivier Houchard <cognet@FreeBSD.org> |
Don't add a bwrite() symbol, it breaks the build when building newfs statically. Instead, bring in a stripped down version of sbwrite(), and add the offset to every bwrite() calls.
|
Revision tags: release/7.1.0_cvs, release/7.1.0 |
|
#
e57c2b13 |
| 04-Dec-2008 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
integrate from head@185615
|
#
64c8fef5 |
| 03-Dec-2008 |
Luigi Rizzo <luigi@FreeBSD.org> |
Enable operation of newfs on plain files, which is useful when you want to prepare disk images for emulators (though 'makefs' in port can do something similar).
This relies on: + minor changes to pa
Enable operation of newfs on plain files, which is useful when you want to prepare disk images for emulators (though 'makefs' in port can do something similar).
This relies on: + minor changes to pass the consistency checks even when working on a file;
+ an additional option, '-p partition' , to specify the disk partition to initialize;
+ some changes on the I/O routines to deal with partition offsets.
The latter was a bit tricky to implement, see the details in newfs.h: in newfs, I/O is done through libufs which assumes that the file descriptor refers to the whole partition. Introducing support for the offset in libufs would require a non-backward compatible change in the library, to be dealt with a version bump or with symbol versioning.
I felt both approaches to be overkill for this specific application, especially because there might be other changes to libufs that might become necessary in the near future.
So I used the following trick: - read access is always done by calling bread() directly, so we just add the offset in the (few) places that call bread(); - write access is done through bwrite() and sbwrite(), which in turn calls bwrite(). To avoid rewriting sbwrite(), we supply our own version of bwrite() here, which takes precedence over the version in libufs.
MFC after: 4 weeks
show more ...
|
Revision tags: release/6.4.0_cvs, release/6.4.0 |
|
#
a6a56870 |
| 06-Mar-2008 |
Xin LI <delphij@FreeBSD.org> |
Use calloc().
|
Revision tags: release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0 |
|
#
59c0f728 |
| 16-Dec-2007 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Report erase interval (correctly) in sectors.
|
#
9a6378d8 |
| 16-Dec-2007 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Rename the undocumented -E option to -X.
Implement -E option which will erase the filesystem sectors before making the new filesystem. Reserved space in front of the superblock (bootcode) is not er
Rename the undocumented -E option to -X.
Implement -E option which will erase the filesystem sectors before making the new filesystem. Reserved space in front of the superblock (bootcode) is not erased.
NB: Erasing can take as long time as writing every sector sequentially.
This is relevant for all flash based disks which use wearlevelling.
show more ...
|
Revision tags: release/6.2.0_cvs, release/6.2.0 |
|
#
868c68ed |
| 31-Oct-2006 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Add -J flag to both newfs(8) and tunefs(8) which allows to enable gjournal support. I left -j flag for UFS journal implementation which we may gain at some point.
Sponsored by: home.pl
|
#
3a6ab3de |
| 27-Sep-2006 |
Xin LI <delphij@FreeBSD.org> |
Explicitly say which gid do we use as a fallback, when operator is not found.
Suggested by: kensmith
|
Revision tags: release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0 |
|
#
9405aea2 |
| 14-Aug-2005 |
Ian Dowse <iedowse@FreeBSD.org> |
Don't treat failure to find the operator GID as a fatal error; this made it impossible to use newfs (and mdmfs) when /etc/group is missing and /etc is read-only.
|
Revision tags: release/5.4.0_cvs, release/5.4.0 |
|
#
3ae329b8 |
| 20-Feb-2005 |
Xin LI <delphij@FreeBSD.org> |
When creating a new FFS file system, the block size will indirectly affect the largest file size that is allowed by the file system. On the other hand, when creating a snapshot, the snapshot file wil
When creating a new FFS file system, the block size will indirectly affect the largest file size that is allowed by the file system. On the other hand, when creating a snapshot, the snapshot file will appear as it is as big as the file system itself. Hence we will not be able to create a file system on large file systems with small block sizes.
Add a warning about this, and gives some hints to correct the issue.
Reviewed by: mckusick MFC After: 1 week
show more ...
|
#
34b59b6b |
| 21-Jan-2005 |
Wes Peters <wes@FreeBSD.org> |
Add an option to suppress the creation of the .snap directory in the new filesystem. This is intended for memory and vnode filesystems that will never be fsck'ed or dumped.
Obtained from: St. Berna
Add an option to suppress the creation of the .snap directory in the new filesystem. This is intended for memory and vnode filesystems that will never be fsck'ed or dumped.
Obtained from: St. Bernard Software RAPID MFC after: 2 weeks
show more ...
|
Revision tags: release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0 |
|
#
b72ea57f |
| 19-Aug-2004 |
John Baldwin <jhb@FreeBSD.org> |
Generalize the UFS bad magic value used to determine when a filesystem has only been partly initialized via newfs(8) so that it applies to both UFS1 and UFS2.
Submitted by: "Xin LI" delphij at front
Generalize the UFS bad magic value used to determine when a filesystem has only been partly initialized via newfs(8) so that it applies to both UFS1 and UFS2.
Submitted by: "Xin LI" delphij at frontfree dot net MFC: maybe?
show more ...
|
Revision tags: release/4.10.0_cvs, release/4.10.0 |
|
#
4c723140 |
| 09-Apr-2004 |
Mark Murray <markm@FreeBSD.org> |
Remove advertising clause from University of California Regent's license, per letter dated July 22, 1999.
Approved by: core, imp
|
#
ce20d788 |
| 26-Feb-2004 |
Robert Watson <rwatson@FreeBSD.org> |
Add a "-l" flag to newfs, which sets the FS_MULTILABEL flag. This permits users of newfs to set the multilabel flag on UFS1 and UFS2 file systems from inception without using tunefs.
Obtained from:
Add a "-l" flag to newfs, which sets the FS_MULTILABEL flag. This permits users of newfs to set the multilabel flag on UFS1 and UFS2 file systems from inception without using tunefs.
Obtained from: TrustedBSD Project Sponsored by: DARPA, McAfee Research
show more ...
|
Revision tags: release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0 |
|
#
96982f9b |
| 27-Nov-2003 |
Wes Peters <wes@FreeBSD.org> |
Fix whitespace error in previous commit.
Approved by: RE@ (Robert Watson)
|
#
f44ec7f8 |
| 23-Nov-2003 |
Wes Peters <wes@FreeBSD.org> |
Don't use UFS2_BAD_MAGIC on UFS (v1) filesystems; it is Not Ready for Prime Time there.
Submitted by: Xin LI <delphij@frontfree.net> Approved by: RE@ (John, Scott)
|
#
0af4e34b |
| 16-Nov-2003 |
Wes Peters <wes@FreeBSD.org> |
Add the -E command line option to force error conditions for testing.
Sponsord by: St. Bernard Software
|
#
ec52df8e |
| 16-Nov-2003 |
Wes Peters <wes@FreeBSD.org> |
Write the UFS2 superblock with a 'BAD' magic number at the beginning of newfs, to signify the newfs operation has not yet completed. Re- write the superblock with the correct magic number once all o
Write the UFS2 superblock with a 'BAD' magic number at the beginning of newfs, to signify the newfs operation has not yet completed. Re- write the superblock with the correct magic number once all of the cylinder groups have been created to show the operation has finished.
Sponsored by: St. Bernard Software
show more ...
|