> On Mon, 11 Jun 2018 19:32:45 +0000 (UTC) > Warner Losh <i...@freebsd.org> wrote: > > > Author: imp > > Date: Mon Jun 11 19:32:45 2018 > > New Revision: 334971 > > URL: https://svnweb.freebsd.org/changeset/base/334971 > > > > Log: > > Document the newly enforced 524288 inode restriction. > > > > Modified: > > head/sbin/dump/dump.8 > > > > Modified: head/sbin/dump/dump.8 > > ============================================================================== > > --- head/sbin/dump/dump.8 Mon Jun 11 19:32:40 2018 (r334970) > > +++ head/sbin/dump/dump.8 Mon Jun 11 19:32:45 2018 (r334971) > > @@ -29,7 +29,7 @@ > > .\" @(#)dump.8 8.3 (Berkeley) 5/1/95 > > .\" $FreeBSD$ > > .\" > > -.Dd October 3, 2016 > > +.Dd June 11, 2018 > > .Dt DUMP 8 > > .Os > > .Sh NAME > > @@ -566,3 +566,8 @@ This will be fixed in a later version of > > .Fx . > > Presently, it works if you set it setuid (like it used to be), but this > > might constitute a security risk. > > +.Pp > > +It is not possible to safely dump filesystems that use more than > > +524288 inodes. > > +.Nm > > +refuses to dump any filesystem that has more than 524288 inodes. > > _______________________________________________ > > svn-src-head@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/svn-src-head > > To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org" > > Hello. > > Is this limitation going to be eternal or are efforts being made to make it > possible to go beyond this limitations? Just for curiosity ... > > Thanks in advance,
This 512k limitiation was a short lived miss understanding of the code and a correct fix that should resolve the issue has been commited, I am doing futher testing at this time on a large file system to confirm imp@'s fix. -- Rod Grimes rgri...@freebsd.org _______________________________________________ svn-src-head@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
