All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Strange file system errors
Date: Wed Jan 14 18:22:01 2004	[thread overview]
Message-ID: <20040114142444.GA2837@redhat.com> (raw)
In-Reply-To: <20040114113509.GA745@glorybox.de>

On Wed, Jan 14, 2004 at 12:35:09PM +0100, Kai Weber wrote:
> Hi,
> 
> if I have to reboot my system without a clean shutdown the recovered
> filesystems are corrupt. Files which I edited recently and maybe not yet
> written to the buffer are recovered with no or corrupt contents. 
> 
> For example:
> 
> $ ls -l config
> -rw-------    1 bond     bond        19622 Jan 14 12:04 .config
> $ stat config
>   File: `config'
>   Size: 19622           Blocks: 0          IO Block: 4096   regular file
> Device: fe01h/65025d    Inode: 20967432    Links: 1
> Access: (0600/-rw-------)  Uid: ( 1000/    bond)   Gid: ( 1000/    bond)
> Access: 2004-01-14 12:27:01.000000000 +0100
> Modify: 2004-01-14 12:04:16.000000000 +0100
> Change: 2004-01-14 12:04:16.000000000 +0100
> $ cat config
> $ less config
> "config" may be a binary file.  See it anyway?
> ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
> [...]
> $ strace -e write cat config
> write(1, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 4096
> write(1, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 4096
> write(1, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 4096
> write(1, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 4096
> write(1, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 3238) = 3238
> 
> I can force this error by pressing the reset button with an open file in my
> text editor. It seems to have nothing to do with the underlying file
> system. I have XFS and ext3 partitions. I would like to know, if it is a
> LVM problem. 

No.

> 
> Kernel 2.6.1
> LVM version:     2.00.08 (2003-11-14)
> Library version: 1.00.07-ioctl (2003-11-21)
> Driver version:  4.0.0
> 
> -- 
>   Kai Weber
> » kai.weber@glorybox.de
>   http://www.glorybox.de
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2004-01-14 18:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14  6:36 [linux-lvm] Strange file system errors Kai Weber
2004-01-14 18:22 ` Heinz Mauelshagen [this message]
2004-01-14 18:44   ` Kai Weber
2004-01-14 19:17     ` Jord Tanner
2004-01-16 12:31       ` Kai Weber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040114142444.GA2837@redhat.com \
    --to=mauelshagen@redhat.com \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.