public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Parpart <trapni@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Which filesystem for a notebook?
Date: Tue, 9 Aug 2005 20:46:21 +0200	[thread overview]
Message-ID: <200508092046.23474.trapni@gentoo.org> (raw)
In-Reply-To: <42F8F27F.5030303@gonoph.net>

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

On Tuesday 09 August 2005 20:14, Billy Holmes wrote:
[....]
> I use ext3 on an external harddrive, as I believe in the data recovery
> aspects of ext3. For my desktop machines, I use xfs. For servers, I use
> ext3 unless I really feel I need the extra performance, then I use xfs.

You really *do* speak out of my mind ;-) Well, I share the same oppinions 
about these FSs and have the same fs setups as you (obviousely!).

> > I do not know of any Linux filesystem that can be resized while still
> > mounted.
>
> $ man xfs_growfs
[...]
> you *must* have the filesystem mounted in order to use xfs_growfs. XFS
> lends itself VERY well to lvm2 (which also runs on all my desktops).

This confused me the first time I wanted to growfs my /home; However, it has 
been a little bit funny aswell, as ext3 (originally) only supported offline 
growings.

However, I once have (accidently!) thrown down one harddrive of mine from 
within 60cm distance down while moving to a new tower/rac; I were nearly 
crying about, but before, I quickly invoked fsck.xfs on my LVM (which this 
disk is part of) and *really* got confused.
fsck.xfs is really a no-op. I couldn't figure out yet why. I can now just pray 
that everything seems to go just well (as it does till now ;)

Regards,
Christian Parpart.

-- 
 20:26:55 up 139 days,  9:34,  2 users,  load average: 0.09, 0.08, 0.08

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

  reply	other threads:[~2005-08-09 18:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 21:40 [gentoo-user] Which filesystem for a notebook? Alexander Skwar
2005-08-09  1:30 ` Bob Sanders
2005-08-09  9:33   ` Ow Mun Heng
2005-08-09 20:47     ` Bob Sanders
2005-08-13 11:29       ` Fernando Meira
2005-08-13 11:59         ` Neil Bothwick
2005-08-13 12:24           ` Fernando Meira
2005-08-13 12:37             ` Neil Bothwick
2005-08-13 15:58         ` Uwe Thiem
2005-08-09  1:51 ` Volker Armin Hemmann
2005-08-09  3:24   ` Richard Fish
2005-08-09  5:32     ` Michael Crute
2005-08-09  8:00     ` Neil Bothwick
2005-08-09 13:38       ` A. R.
2005-08-09 13:42       ` Mauro Faccenda
2005-08-09 13:40         ` Mike Williams
2005-08-09 13:54         ` Dirk Heinrichs
2005-08-09 14:29         ` Neil Bothwick
2005-08-09 15:09       ` Richard Fish
2005-08-09 15:41         ` Neil Bothwick
2005-08-09 18:14     ` Billy Holmes
2005-08-09 18:46       ` Christian Parpart [this message]
2005-08-09 20:36         ` Volker Armin Hemmann
2005-08-10 15:49         ` [gentoo-user] Dropping harddrives (WAS Which filesystem for a notebook?) Billy Holmes
2005-08-10 15:57           ` Chad Leigh -- Shire.Net LLC
2005-08-10 16:14             ` Billy Holmes
2005-08-10 18:02               ` Chad Leigh -- Shire.Net LLC
2005-08-10 20:42               ` Craig Zeigler
2005-08-16 18:19     ` [gentoo-user] Which filesystem for a notebook? Alexander Skwar

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=200508092046.23474.trapni@gentoo.org \
    --to=trapni@gentoo.org \
    --cc=gentoo-user@lists.gentoo.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