Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Hugo Mills <hugo@carfax.org.uk>
To: MegaBrutal <megabrutal@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS over LVM remounts read-only
Date: Sat, 11 Jan 2014 15:04:54 +0000	[thread overview]
Message-ID: <20140111150454.GV15634@carfax.org.uk> (raw)
In-Reply-To: <CAE8gLh=drhPtUXSbT7zHDSh7pipxuZpVhfuRQ7QOFV+HP4wHPQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2380 bytes --]

On Sat, Jan 11, 2014 at 03:32:26PM +0100, MegaBrutal wrote:
> Hello,
> 
> I'm using BTRFS over LVM and after some time of usage (days or hours),
> it just remounts itself, and I don't see the reason why, while it is
> said to be fault-tolerant.
> 
> It is possible that I have bad sectors on the disk, though I don't
> find it likely. Even then, I don't think bad sectors should cause that
> much of a problem that the FS needs to be remounted because of it. Is
> there a way to make BTRFS to detect and mark bad sectors like any
> other file system does?
> 
> Here are the /etc/fstab entries those concern my BTRFS file system:
> /dev/mapper/vmhost--vg-vmhost--rootfs /               btrfs
> defaults,subvol=@ 0       1
> /dev/mapper/vmhost--vg-vmhost--rootfs /home           btrfs
> defaults,subvol=@home 0       2
> /dev/mapper/vmhost--vg-vmhost--rootfs /media/btrfs    btrfs   noauto
>          0       3
> 
> I've attached a dmesg output that may help developers to see what's the problem.
> 
> Do you have any ideas what causes the problem?

[60631.481913] attempt to access beyond end of device
[60631.481935] dm-1: rw=1073, want=42917896, limit=42917888
[60631.481941] btrfs_dev_stat_print_on_error: 34 callbacks suppressed
[60631.481949] btrfs: bdev /dev/mapper/vmhost--vg-vmhost--rootfs errs: wr 311347, rd 0, flush 0, corrupt 0, gen 0

   This is the problem.

   It looks like you've shrunk the LV without first shrinking the
filesystem. Depending on how much you shrunk it by, the odds are
fairly good that significant chunks of the FS are now toast.

   Hugo.

> Also, if the disaster happens and the FS gets remounted read-only, is
> there a way to force remount it in read-write mode? I've tried "mount
> -o remount,rw" and "mount -o force,remount,rw" too, but it doesn't
> work. Also I can't mount the BTRFS root or any subvolumes elsewhere
> until I restart the system.
> 
> Probably my description of the problem wasn't detailed enough, but
> since I'm totally clueless about the problem (not counting the
> possible bad sectors), I can't tell more right now. But you can ask
> more details and I'll try to answer.
> 
> 
> MegaBrutal



-- 
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
  PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
     --- Gomez, darling, don't torture yourself.  That's my job. ---     

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2014-01-11 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11 14:32 BTRFS over LVM remounts read-only MegaBrutal
2014-01-11 15:04 ` Hugo Mills [this message]
2014-01-11 17:10   ` MegaBrutal
2014-01-11 17:28     ` Hugo Mills
2014-01-11 18:03     ` Chris Murphy
2014-01-11 18:48     ` Szalma László
2014-01-11 19:16       ` Roman Mamedov
2014-01-11 19:24         ` Szalma László
2014-01-11 23:08         ` Chris Murphy
2014-01-11 23:03       ` Chris Murphy
2014-01-12  4:44         ` Duncan

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=20140111150454.GV15634@carfax.org.uk \
    --to=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=megabrutal@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox