From: Goffredo Baroncelli <kreijack@libero.it>
To: CACook@quantum-sci.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Kernel Modules
Date: Sun, 10 Jul 2011 10:24:26 +0200 [thread overview]
Message-ID: <4E1961BA.8020603@libero.it> (raw)
In-Reply-To: <201107091028.04403.CACook@quantum-sci.com>
On 07/09/2011 07:28 PM, CACook@quantum-sci.com wrote:
> On Saturday 9 July, 2011 10:12:43 you wrote:
>> If your btrfs lives on two or more devices you will have to run
>> 'btrfs device scan' prior to mount or give all devices as arguments
>> to mount.btrfs.
>
> Ohhh, I'd added a disk drive without modifying fstab. Thanks.
>
> Where would you put a device scan to happen at boot?
The more recent distro put the scanning logic in the initrd. This should
be the right place.
> On another subject, I guess there are two ways to remove old snapshot
> directories: - btrfs subvolume delete - rm -rf
with rm -rf you can remove only the subvolume contents, but you cannot
delete a subvoulume.
>
> I understand that snapshots are cumulative for files and do not
> duplicate, but is it necessary to use the subvolume delete command to
> preserve the integrity of remaining snapshots?
No. Apart removing the subvolume entry, "rm -rf" and "btrfs subvolume
delete" reach the same result. The latter is only a lot more efficient.
> And also, about once a week KDE locks up on me after a suspend, and I
> have to power-cycle it. Is there any maintenance I should do on a
> btrfs part when this happens?
Normally you don't do anything. In any case you are not able to do
anything because there no is a tool like fsck available :-)
>
> -- To unsubscribe from this list: send the line "unsubscribe
> linux-btrfs" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html .
>
next prev parent reply other threads:[~2011-07-10 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-09 16:19 Kernel Modules CACook
2011-07-09 17:12 ` Andreas Philipp
2011-07-09 17:28 ` CACook
2011-07-09 17:39 ` Hugo Mills
2011-07-10 8:24 ` Goffredo Baroncelli [this message]
2011-07-09 17:33 ` Helmut Hullen
2011-07-10 6:56 ` Felix Blanke
2011-07-10 7:29 ` Helmut Hullen
2011-07-10 14:24 ` Felix Blanke
2011-07-10 15:57 ` Helmut Hullen
2011-07-10 16:42 ` Felix Blanke
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=4E1961BA.8020603@libero.it \
--to=kreijack@libero.it \
--cc=CACook@quantum-sci.com \
--cc=kreijack@inwind.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).