On Tue, Nov 02, 2010 at 07:33:50PM +, Bruce Cran wrote:
On Tuesday 02 November 2010 19:12:14 Bruce Cran wrote:
I've noticed in recent months that I appear to be getting silent corruption
of my UFS filesystems - and I think it may be linked to using md(4) or
creating sparse files.
I've noticed in recent months that I appear to be getting silent corruption of
my UFS filesystems - and I think it may be linked to using md(4) or creating
sparse files.
I created a 20GB md device using truncate -s 20G mdfile mdconfig -a -f
mdfile and then ran some gpart commands before using
On Tuesday 02 November 2010 19:12:14 Bruce Cran wrote:
I've noticed in recent months that I appear to be getting silent corruption
of my UFS filesystems - and I think it may be linked to using md(4) or
creating sparse files.
I've confirmed this is a UFS bug related to sparse files: truncate
On Tue, Nov 02, 2010 at 07:33:50PM +, Bruce Cran wrote:
On Tuesday 02 November 2010 19:12:14 Bruce Cran wrote:
I've noticed in recent months that I appear to be getting silent corruption
of my UFS filesystems - and I think it may be linked to using md(4) or
creating sparse files.
On Tuesday 02 November 2010 19:57:32 Kostik Belousov wrote:
What is .viminfo ? How is it related to the command you have shown ?
What are exact mount options you are using ?
.viminfo is a file created by vim containing various bits of session
information. I don't know why it gets corrupted,
On 11/02/2010 20:37, Bruce Cran wrote:
On Tuesday 02 November 2010 19:57:32 Kostik Belousov wrote:
What is .viminfo ? How is it related to the command you have shown ?
What are exact mount options you are using ?
.viminfo is a file created by vim containing various bits of session
