Growfs has a 32bit integer internall, where it should have a 64bit. This has the effect that filesystems over a certain size cant be enlarged.
Hi Growfs team
I believe i have uncovered a bug in growfs related to 32bit integers.
My original enquirey to freebsd-fs@freebsd is archived at ...
You can see that i have enlarged a disk where i had previous formatted it
without slices/partitions. I then wanted to grow the filesystem to match.
I dont believer there is a problem with the slices/noslices side of
things, but i believe there is an integer looping inside growfs which is
causing it to refuse to enlarge.
I poked around in the source code and i believe that the p_size variable
should be 64bit.
Some googling shows support for this theory...
here is another person reporting the same problem as myself
first post -
discussion about p_size -
further discussion -
here is a much more recent thread with the same sort of problem
which includes a link to patch for an older version of growfs
Which expands upon the changes outlined in the 'fixunix.com' discussion.
I am hoping that you can make appropriate changes in growfs and release
them in to freebsd.
Thank you for your good work.
How-To-Repeat: Try to enlarge a filesystem whos size is beyond 2^32
Assign to freebsd-fs@, since they should have an opinion regarding this issue.
For bugs matching the following criteria:
Status: In Progress Changed: (is less than) 2014-06-01
Reset to default assignee and clear in-progress tags.
Mail being skipped
The 'p_size' variable does not exist since base r234846; is it still an issue?