Date: Tue, 6 Jan 2009 19:53:59 -0800 From: "Garrett Cooper" <yanefbsd@gmail.com> To: "Tom Samplonius" <tom@samplonius.org> Cc: SDH Admin <admin@stardothosting.com>, freebsd-stable@freebsd.org Subject: Re: ver 4.2 won't allow save because it can't see 2.2T disk drive Message-ID: <7d6fde3d0901061953s5f623082u8cab20a0902e554a@mail.gmail.com> In-Reply-To: <17218792.31231294718710.JavaMail.root@ly.sdf.com> References: <006401c96477$3dd8e440$b98aacc0$@com> <17218792.31231294718710.JavaMail.root@ly.sdf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 6, 2009 at 6:18 PM, Tom Samplonius <tom@samplonius.org> wrote: > > ----- "SDH Admin" <admin@stardothosting.com> wrote: > >> >I need to patch this until I can update the system, any pointers to >> >where (if there is one) to get the patch for this, and installation >> >instructions. >> >> What is the 2.2T disk formatted as? Can you give more details on your >> hardware (storage device and the 4.2 server), as well as posting your >> dmesg >> output. > > In this case, it is pretty clear the the 2.2TB disk is mounted on NFS. And the OP said it was a StorageVault, so that means it is a WAFL filesystem, which is meaningless here. > > Is it really FreeBSD 4.2? > > Anyways, it doesn't really matter what "df" reports. If df is folding some of the 64bit values in negative numbers, it is no issue really. But if the StorageVault is returning errors when files are created or written to, then that is probably a configuration issue. > > NFS is a client-server filesystem. So "df" on NFS just queries the StorageVault for the info, and displays it. The NFS client doesn't shutdown, because the filesystem appear to be full, or have negative capacity. > > Tom Are you perhaps referring to OpenBSD 4.2 0-0? -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7d6fde3d0901061953s5f623082u8cab20a0902e554a>