History log of /freebsd/sbin/growfs/growfs.c (Results 126 – 150 of 161)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# adcaff07 07-Jun-2001 Thomas-Henning von Kamptz <tomsoft@FreeBSD.org>

cleanup to get rid of most warnings on alpha
and yes now it also works on alpha

Reviewed by: chm
MFC after: 3 weeks


# 25e34650 05-Jun-2001 Thomas-Henning von Kamptz <tomsoft@FreeBSD.org>

fix a bug of a only partitally initialization which could result
in an unclean filesystem after growing by a large amount of cylinder
groups

Reviewed by: chm


Revision tags: release/4.3.0_cvs, release/4.3.0
# 4020c5bc 12-Dec-2000 Thomas-Henning von Kamptz <tomsoft@FreeBSD.org>

corrected spelling mistakes in comments
check a couple of mallocs
usage of errx
linebreaks of DBG_ macros,
correcting the usage of nroff macros

Submitted by: grog, charnier
Reviewed by: chm


# 3d500078 09-Dec-2000 Thomas-Henning von Kamptz <tomsoft@FreeBSD.org>

added growfs(8) including ffsinfo(8) to the freebsd base system

Reviewed by: grog


# 08f353eb 13-Feb-2010 Gavin Atkinson <gavin@FreeBSD.org>

When growing a UFS1 filesystem, we need to initialise all inodes in any new
cylinder groups that are created. When the filesystem is first created,
newfs always initialises the first two blocks of i

When growing a UFS1 filesystem, we need to initialise all inodes in any new
cylinder groups that are created. When the filesystem is first created,
newfs always initialises the first two blocks of inodes, and then in the
UFS1 case will also initialise the remaining inode blocks. The changes in
growfs.c 1.23 broke the initialisation of all inodes, seemingly based on
this implementation detail in newfs(8). The result was that instead of
initialising all inodes, we would actually end up initialising all but the
first two blocks of inodes. If the filesystem was grown into empty
(all-zeros) space then the resulting filesystem was fine, however when
grown onto non-zeroed space the filesystem produced would appear to have
massive corruption on the first fsck after growing.
A test case for this problem can be found in the PR audit trail.

Fix this by once again initialising all inodes in the UFS1 case.

PR: bin/115174
Submitted by: Nate Eldredgei nge cs.hmc.edu
Reviewed by: mjacob
MFC after: 1 month

show more ...


# 14a176a0 11-Feb-2010 Kirk McKusick <mckusick@FreeBSD.org>

Quiet spurious warnings.


# 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.


# eb747250 02-Jan-2010 Gavin Atkinson <gavin@FreeBSD.org>

Remove dead code. This section of code is only run in the
(sblock.fs_magic == FS_UFS1_MAGIC) case, so the check within the
loop is redundant.

Submitted by: Nate Eldredge nge cs.hmc.edu
Reviewed by

Remove dead code. This section of code is only run in the
(sblock.fs_magic == FS_UFS1_MAGIC) case, so the check within the
loop is redundant.

Submitted by: Nate Eldredge nge cs.hmc.edu
Reviewed by: mjacob
Approved by: ed (mentor)
MFC after: 1 month

show more ...


Revision tags: release/8.0.0_cvs, release/8.0.0
# 874108ae 12-Nov-2009 Oleksandr Tymoshenko <gonzo@FreeBSD.org>

MFC @199204


# 4bdcc9c7 05-Oct-2009 Matt Jacob <mjacob@FreeBSD.org>

The cylinder group tag cg_initediblk needs to match the number of inodes
actually initialized. In the growfs case for UFS2, no inodes were actually
being initialized and the number of inodes noted as

The cylinder group tag cg_initediblk needs to match the number of inodes
actually initialized. In the growfs case for UFS2, no inodes were actually
being initialized and the number of inodes noted as initialized was the
number of inodes per group. This created a filesystem that was deemed
corrupted because the inodes thus added were full of garbage.

MFC after: 1 month

show more ...


Revision tags: release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0
# baa15be0 17-Dec-2007 David Schultz <das@FreeBSD.org>

Fix an int overflow on very large file systems.

PR: bin/113399
Submitted by: Staffan Ulfberg <staffan@ulfberg.se>


Revision tags: release/6.2.0_cvs, release/6.2.0
# 42e35587 17-Jul-2006 Stefan Farfeleder <stefanf@FreeBSD.org>

Remove duplicated assignment.


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, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0
# e3ec673e 16-Jan-2005 Philippe Charnier <charnier@FreeBSD.org>

Remove \n at the end of err(3) strings


Revision tags: release/5.3.0_cvs, release/5.3.0
# e7c46054 09-Oct-2004 Scott Long <scottl@FreeBSD.org>

3 important fixes for growfs:

1) ginode() is passed a cylinder group number and inode number. The inode
number is relative to the cg. Use this relative number rather than the
absolute inode number

3 important fixes for growfs:

1) ginode() is passed a cylinder group number and inode number. The inode
number is relative to the cg. Use this relative number rather than the
absolute inode number when searching the cg inode bitmap to see if the inode
is allocated. Using the absolute number quickly runs the check off the end
of the array and causes invalid inodes to be referenced.

2) ginode() checks the absolute indoe number to make sure that it is greater
than ROOTINO. However, the caller loops through all of the possible inode
numbers and directly passes in values that are < ROOTINO. Instead of halting
the program with an error, just return NULL.

3) When allocating new cylinder groups, growfs was initializing all of the
inodes in the group regardless of this only being required for UFS1. Not
doing this for UFS2 provides a significant performance increase.

These fixes allow growing a filesystem beyond a trivial amount and have
been tested to grow an 8GB filesystem to 1.9TB. Much more testing would
be appreciated.

Obtained from: Sandvine, Inc.

show more ...


# 691ae404 29-Jul-2004 Lukas Ertl <le@FreeBSD.org>

Catch up with recent gcc changes and introduce a DIP_SET macro
to use when setting values that depend on the UFS version.
Raise WARNS again.


Revision tags: release/4.10.0_cvs, release/4.10.0
# 35cf80de 04-Apr-2004 Bruce Evans <bde@FreeBSD.org>

Include <time.h> instead of depending on namespace pollution in <sys/stat.h>
for the declaration of time().


# b1fddb23 04-Apr-2004 Maxime Henrion <mux@FreeBSD.org>

Fix the remaining warnings of growfs(8) on my sparc64 box with
WARNS=6. I don't change the WARNS level in the Makefile because I
didn't tested this on other archs.

The fs.h fix was suggested by: ma

Fix the remaining warnings of growfs(8) on my sparc64 box with
WARNS=6. I don't change the WARNS level in the Makefile because I
didn't tested this on other archs.

The fs.h fix was suggested by: marcel
Reviewed by: md5(1)

show more ...


# 760ea1fa 04-Apr-2004 Maxime Henrion <mux@FreeBSD.org>

- Don't abuse caddr_t when what we really want is a void *.
- Use the %jd format and a cast to intmax_t to print an int64_t.
- The return type of getopt() is an int, not a char.

This fixes some warn

- Don't abuse caddr_t when what we really want is a void *.
- Use the %jd format and a cast to intmax_t to print an int64_t.
- The return type of getopt() is an int, not a char.

This fixes some warnings but there's still much more work to do here.

show more ...


# 75d1ec91 03-Apr-2004 Lukas Ertl <le@FreeBSD.org>

Make growfs WARNS=6 clean.

Approved by: grog (mentor)


# f055f9f2 27-Mar-2004 Lukas Ertl <le@FreeBSD.org>

Don't read an inode which isn't used to avoid problems on UFS2 where not
all inodes are initialized when running newfs.

Approved by: grog (mentor)


Revision tags: release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0
# 654c2874 30-Oct-2003 Tom Rhodes <trhodes@FreeBSD.org>

Remove a few unused variables.


Revision tags: release/4.9.0_cvs, release/4.9.0, release/5.1.0_cvs, release/5.1.0
# 4b9748d4 12-May-2003 Greg Lehey <grog@FreeBSD.org>

Understand GEOM. This makes growfs work again, but it really needs rewriting.

Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
Approved by: re (scottl)


# 6ded0533 26-Apr-2003 Jens Schweikhardt <schweikh@FreeBSD.org>

Fix typos in comments; some style(9) fixes; no code changes.

PR: misc/50979
Submitted by: Lukas Ertl <l.ertl@univie.ac.at>


Revision tags: release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0
# d64ada50 30-Dec-2002 Jens Schweikhardt <schweikh@FreeBSD.org>

Fix typos, mostly s/ an / a / where appropriate and a few s/an/and/
Add FreeBSD Id tag where missing.


# ada981b2 27-Nov-2002 Kirk McKusick <mckusick@FreeBSD.org>

Create a new 32-bit fs_flags word in the superblock. Add code to move
the old 8-bit fs_old_flags to the new location the first time that the
filesystem is mounted by a new kernel. One of the unused f

Create a new 32-bit fs_flags word in the superblock. Add code to move
the old 8-bit fs_old_flags to the new location the first time that the
filesystem is mounted by a new kernel. One of the unused flags in
fs_old_flags is used to indicate that the flags have been moved.
Leave the fs_old_flags word intact so that it will work properly if
used on an old kernel.

Change the fs_sblockloc superblock location field to be in units
of bytes instead of in units of filesystem fragments. The old units
did not work properly when the fragment size exceeeded the superblock
size (8192). Update old fs_sblockloc values at the same time that
the flags are moved.

Suggested by: BOUWSMA Barry <freebsd-misuser@netscum.dyndns.dk>
Sponsored by: DARPA & NAI Labs.

show more ...


1234567