public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Extended file attributes: ext4
Date: Sun, 8 Apr 2012 18:44:30 +0200	[thread overview]
Message-ID: <20120408164430.GD3025@solfire> (raw)
In-Reply-To: <201204081734.11781.michaelkintzios@gmail.com>

Mick <michaelkintzios@gmail.com> [12-04-08 18:40]:
> On Sunday 08 Apr 2012 16:56:23 David W Noon wrote:
> > On Sun, 8 Apr 2012 17:26:03 +0200, meino.cramer@gmx.de wrote about
> > 
> > [gentoo-user] Extended file attributes: ext4:
> > > is it possible to go from an ext4-filesystem with no extended file
> > > attributes to one with extended file attributes without reformatting
> > > the disk or other very risky low level things just by adding this
> > > feature to the kenrel (?) ?
> > 
> > Yes, it's simple.
> > 
> > You need to ensure that your kernel configuration has the extended
> > attribute support (ACL is a good idea too) and you have booted with the
> > ext4 driver so configured.
> > 
> > You then add the xattr option in /etc/fstab for the filesystem(s) where
> > you want extended attribute support.  If you do that before you reboot
> > (as above) then you will have full extended attribute support.
> 
> I thought that you are meant to pass such options on the CLI at the time you 
> are formatting the partition ... is this incorrect?
> 
> Of course if you must format the drive with such options then the data won't 
> survive.
> -- 
> Regards,
> Mick


Hi,

thank you very much for all the input.

To clearify things a little:

Status quo: System with ext4 and no extended attributes.
Where I want to be: The same system with extended attributes.

Way to go: No reformatting and mkfs and all that things. Only kernel
reconfiguring / recompiling / rebooting and emerging some tools.

Possible?

Best regards,
mcc




  reply	other threads:[~2012-04-08 16:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-08 15:26 [gentoo-user] Extended file attributes: ext4 meino.cramer
2012-04-08 15:56 ` David W Noon
2012-04-08 16:34   ` Mick
2012-04-08 16:44     ` meino.cramer [this message]
2012-04-08 17:36       ` [gentoo-user] " Nikos Chantziaras
2012-04-08 18:21       ` [gentoo-user] " Canek Peláez Valdés
2012-04-08 18:37         ` meino.cramer
2012-04-08 18:41         ` Michael Mol
2012-04-08 18:51           ` Canek Peláez Valdés
2012-04-08 18:59             ` Michael Mol
2012-04-08 19:00               ` Michael Mol
2012-04-08 19:04               ` Canek Peláez Valdés
2012-04-08 19:19                 ` Michael Mol
2012-04-09 10:06         ` Stroller
2012-04-09 10:23           ` Canek Peláez Valdés
2012-04-09 11:35             ` Stroller
2012-04-09 12:03               ` Neil Bothwick
2012-04-09 12:04               ` Canek Peláez Valdés
2012-04-10 11:00                 ` Stroller
2012-04-10 17:01                   ` Canek Peláez Valdés
2012-04-09 14:09           ` Michael Mol
2012-04-10  9:55             ` Stroller
2012-04-12 22:24         ` Frank Steinmetzger
2012-04-12 22:43           ` Frank Steinmetzger
2012-04-13  2:23           ` Canek Peláez Valdés
2012-04-08 17:34     ` [gentoo-user] " Nikos Chantziaras
2012-04-08 17:59       ` Mick

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=20120408164430.GD3025@solfire \
    --to=meino.cramer@gmx.de \
    --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