All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rosario Turrisi <turrisi@pd.infn.it>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: action "debugfs-like" through nfs?
Date: Wed, 23 Jul 2003 17:15:24 +0200	[thread overview]
Message-ID: <3F1EA68C.7020700@pd.infn.it> (raw)
In-Reply-To: <shs1xwhtgzv.fsf@charged.uio.no>

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

... because raidtec does not give the password to customers...
I am afraid, and you confirm, that the only choice is their  intervention...
Thanks,
         Rosario

Trond Myklebust wrote:

>>>>>>" " == Rosario Turrisi <turrisi@pd.infn.it> writes:
>>>>>>            
>>>>>>
>
>     > Hi, I have a fileserver from Raidtec which uses ext2
>     > filesystems.  Due to a double (!!!) disk failure, I had the
>     > strange behaviour that a directory is seen as a whole file,
>     > with strange attributes, like "?r--r-sr-T" and changed
>     > owner/group.  I believe that an operation like "debugfs" could
>     > fix the problem, but it cannot be done (it seems) on an
>     > nfs-mounted filesystem (I cannot enter the fileserver system as
>     > it is "raidtec-copyrighted").  Any suggestion very very
>     > welcome.  Cheers,
>
>Errr... Why is fixing it on the server itself (where "debugfs" is more
>likely to work) not an option?
>
>The NFS protocol has no support for doing low-level disk ioctls on the
>server so you can forget doing this sort of thing on the client.
>
>Cheers,
>  Trond
>
>
>
>  
>

[-- Attachment #2: Type: text/html, Size: 1861 bytes --]

      reply	other threads:[~2003-07-23 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 13:10 action "debugfs-like" through nfs? Rosario Turrisi
2003-07-23 15:11 ` Trond Myklebust
2003-07-23 15:15   ` Rosario Turrisi [this message]

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=3F1EA68C.7020700@pd.infn.it \
    --to=turrisi@pd.infn.it \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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.