Date: Wed, 9 Feb 2005 20:09:37 +0200 From: Nikos Vassiliadis <nvass@teledome.gr> To: freebsd-questions@freebsd.org, Nathan Kinkade <nkinkade@ub.edu.bz> Subject: Re: determine ufs2 %fragmentation on mounted filesystem Message-ID: <200502092009.37655.nvass@teledome.gr> In-Reply-To: <20050209173057.GX8365@gentoo-npk.bmp.ub> References: <20050209163433.GW8365@gentoo-npk.bmp.ub> <20050209171039.GD37205@xor.obsecurity.org> <20050209173057.GX8365@gentoo-npk.bmp.ub>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 09 February 2005 19:30, Nathan Kinkade wrote: [snip] > > I had already tried dumpfs, but couldn't find any information about > actual filesystem fragmentation in the output. Erik's suggestion of > running `# fsck -t ufs2 /usr` seemed to work, though I felt a little > skittish about running it on a live filesystem. You can(must) use mksnap_ffs to take a snapshot and fsck that. Note that snapshots are meant to be read-only, so fsck -n, mount -r etc... > It found numerous > errors and auto-answered "no" for all of them, though I never specified > that it should do that. Does fsck just do this by default on a mounted > filesystem? Also, I had tried running fsck manually earlier and the > only difference between what I did and Erik's suggestion was the -t > option, which I wouldn't think should have been necessary. Shouldn't > fsck be able to determine the fs type by looking at the superblock? > > By the way, the fragmentation was as 5.1%. Quite high, and I'm > wondering how it got that way? Squid? > > Thanks, > Nathan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502092009.37655.nvass>