public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Dan Am <xfs@lonx.net>, xfs@oss.sgi.com
Subject: Re: "xfs_io -c chattr +i " on a symlink
Date: Fri, 4 Aug 2006 10:29:50 +1000	[thread overview]
Message-ID: <20060804102949.B2401829@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <44D20473.3010304@sandeen.net>; from sandeen@sandeen.net on Thu, Aug 03, 2006 at 09:13:07AM -0500

On Thu, Aug 03, 2006 at 09:13:07AM -0500, Eric Sandeen wrote:
> Try just using chattr.

Or not. :)

> [sandeen@sandeen ~]$ ln -s /tmp tmplink
> [sandeen@sandeen ~]$ ls -l tmplink
> lrwxrwxrwx  1 sandeen sandeen 4 Aug  3 09:05 tmplink -> /tmp
> [sandeen@sandeen ~]$ su
> Password:
> [root@sandeen sandeen]# chattr +i tmplink
> [root@sandeen sandeen]# stat -f tmplink
>    File: "tmplink"
>      ID: 802      Namelen: 255     Type: XFS (0x58465342)
> Blocks: Total: 23377204   Free: 8557099    Available: 8557099    Size: 4096
> Inodes: Total: 93554496   Free: 93202008
> [root@sandeen sandeen]#
> [root@sandeen sandeen]# lsattr tmplink
> ----i-------- tmplink

... I think you just set immutable on /tmp.  Try a broken symlink,
instead of one that points to an existing inode.

cheers.

-- 
Nathan

  reply	other threads:[~2006-08-04  0:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-03 10:26 "xfs_io -c chattr +i " on a symlink Dan Am
2006-08-03 14:13 ` Eric Sandeen
2006-08-04  0:29   ` Nathan Scott [this message]
2006-08-04  2:38     ` Eric Sandeen
2006-08-04 11:37     ` Dan Am
2006-08-07  4:54       ` Nathan Scott
2006-08-04  0:28 ` Nathan Scott
2006-08-04  4:20   ` Chris Wedgwood
  -- strict thread matches above, loose matches on Subject: below --
2006-08-04  8:15 Dan Am
2006-08-04  9:13 ` Timothy Shimmin
2006-08-03 10:18 Daniel Amthor

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=20060804102949.B2401829@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=sandeen@sandeen.net \
    --cc=xfs@lonx.net \
    --cc=xfs@oss.sgi.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