All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lists <lists@benjamindsmith.com>
To: linux-btrfs@vger.kernel.org
Subject: Hard restart required
Date: Thu, 03 Apr 2014 17:26:46 -0700	[thread overview]
Message-ID: <533DFC46.8020704@benjamindsmith.com> (raw)

Trying out BTRFS today for the first time after a few false starts with 
three drives configured raid1. I'm using Oracle Linux 6/64 with all 
updates applied on unremarkable hardware. (cast off Dell Core2 desktop, 
2 GB RAM, no known problems) Here's what it looks like:

[root@oracle ~]# btrfs filesystem show
Label: none  uuid: bdaf3d87-f992-4a89-9e2b-41de0b5ff909
     Total devices 3 FS bytes used 448.82MB
     devid    2 size 1.36TB used 167.01GB path /dev/sdc
     devid    3 size 1.82TB used 167.01GB path /dev/sdd
     devid    1 size 931.51GB used 2.02GB path /dev/sdb

It hard locked and required a power-off system restart. Is this 
atypical? Here's what did it, this should be OK?

# mount -U bdaf3d87-f992-4a89-9e2b-41de0b5ff909 /media/btrfs;

UUID should work, right? Why else have a UUID if not? Currently, I'm 
using below in /etc/fstab, but this is not preferred since I'm expecting 
hard disks to come and go in my eventual use case - I'm rather certain 
that /dev/sdc will not be the correct drive to mount at some point:

/dev/sdc    /backups/spfs     btrfs noatime,subvol=spfs,compress    0 0


Thanks,

-Ben

             reply	other threads:[~2014-04-04  0:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04  0:26 Lists [this message]
2014-04-04  0:41 ` Hard restart required Avi Miller
2014-04-04 16:26   ` Lists
2014-04-04 21:19     ` Avi Miller
     [not found]       ` <533F3732.6090108@benjamindsmith.com>
2014-04-05  1:48         ` Avi Miller
2014-04-05  1:51           ` Avi Miller
2014-04-04  2:32 ` Anand Jain

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=533DFC46.8020704@benjamindsmith.com \
    --to=lists@benjamindsmith.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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.