inode problem?

inode problem?

[Robert L. Harris]

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



  I have a system at work that seems to have an ext3 filesystem made 
with -T largefile when it really shouldn't have and is running low on 
inodes.  A co-worker has mentioned that reiserfs doesn't have inode 
problems.  I tried to look this up but am having problems 
verifying/denying this:

{0}:Documentation>host www.reiserfs.org
www.reiserfs.org does not exist, try again

Whois also doesn't return anything.  Anyone have any proof either way
and news on the current stability of reiserfs in the 2.4.21 tree?

Robert


:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | GPG Key ID: E344DA3B
                                         @ x-hkp://pgp.mit.edu 
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.

Diagnosis: witzelsucht  	

IPv6 = robert@ipv6.rdlg.net	http://ipv6.rdlg.net
IPv4 = robert@mail.rdlg.net	http://www.rdlg.net

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

Re: inode problem?

[Nikita Danilov]

Robert L. Harris writes:
 > 
 > 
 >   I have a system at work that seems to have an ext3 filesystem made 
 > with -T largefile when it really shouldn't have and is running low on 
 > inodes.  A co-worker has mentioned that reiserfs doesn't have inode 
 > problems.  I tried to look this up but am having problems 
 > verifying/denying this:
 > 
 > {0}:Documentation>host www.reiserfs.org
 > www.reiserfs.org does not exist, try again

$ host www.reiserfs.org
www.reiserfs.org has address 212.16.7.65

(you can also use namesys.com)

 > 
 > Whois also doesn't return anything.  Anyone have any proof either way
 > and news on the current stability of reiserfs in the 2.4.21 tree?

It exists and is stable.

 > 
 > Robert
 > 

Nikita.

 > 

Re: inode problem?

[Hans Reiser]

Robert L. Harris wrote:

>  I have a system at work that seems to have an ext3 filesystem made 
>with -T largefile when it really shouldn't have and is running low on 
>inodes.  A co-worker has mentioned that reiserfs doesn't have inode 
>problems.  I tried to look this up but am having problems 
>verifying/denying this:
>
>{0}:Documentation>host www.reiserfs.org
>www.reiserfs.org does not exist, try again
>
>Whois also doesn't return anything.  Anyone have any proof either way
>and news on the current stability of reiserfs in the 2.4.21 tree?
>
>Robert
>
>
>:wq!
>---------------------------------------------------------------------------
>Robert L. Harris                     | GPG Key ID: E344DA3B
>                                         @ x-hkp://pgp.mit.edu 
>DISCLAIMER:
>      These are MY OPINIONS ALONE.  I speak for no-one else.
>
>Diagnosis: witzelsucht  	
>
>IPv6 = robert@ipv6.rdlg.net	http://ipv6.rdlg.net
>IPv4 = robert@mail.rdlg.net	http://www.rdlg.net
>  
>
inodes are yucky yucky.;-) We ain't got none.

-- 
Hans

Re: inode problem?

[Hans Reiser]

Try www.namesys.com

Robert L. Harris wrote:

>  I have a system at work that seems to have an ext3 filesystem made 
>with -T largefile when it really shouldn't have and is running low on 
>inodes.  A co-worker has mentioned that reiserfs doesn't have inode 
>problems.  I tried to look this up but am having problems 
>verifying/denying this:
>
>{0}:Documentation>host www.reiserfs.org
>www.reiserfs.org does not exist, try again
>
>Whois also doesn't return anything.  Anyone have any proof either way
>and news on the current stability of reiserfs in the 2.4.21 tree?
>
>Robert
>
>
>:wq!
>---------------------------------------------------------------------------
>Robert L. Harris                     | GPG Key ID: E344DA3B
>                                         @ x-hkp://pgp.mit.edu 
>DISCLAIMER:
>      These are MY OPINIONS ALONE.  I speak for no-one else.
>
>Diagnosis: witzelsucht  	
>
>IPv6 = robert@ipv6.rdlg.net	http://ipv6.rdlg.net
>IPv4 = robert@mail.rdlg.net	http://www.rdlg.net
>  
>


-- 
Hans

[OT] Re: inode problem?

[Christian Kujau]

Nikita Danilov schrieb:
>  > {0}:Documentation>host www.reiserfs.org
>  > www.reiserfs.org does not exist, try again
> 
> $ host www.reiserfs.org
> www.reiserfs.org has address 212.16.7.65

evil@prinz:~$ host www.reiserfs.org
www.reiserfs.org does not exist, try again

> (you can also use namesys.com)

yes, that's what im doing because reiserfs.org.
could you tell me your favourite nameserver?

Thanks,
Christian.

evil@prinz:~$ whois reiserfs.org
NOTICE: Access to .ORG WHOIS information is provided to assist persons
[...]

Domain ID:D70636422-LROR
Domain Name:REISERFS.ORG
Created On:09-May-2001 17:02:23 UTC
Last Updated On:09-Jun-2003 21:50:11 UTC
Expiration Date:09-May-2004 17:02:23 UTC
Sponsoring Registrar:R86-LROR
Status:PENDING DELETE
Status:HOLD
Registrant ID:86-C
Registrant Name:SEE SPONSORING REGISTRAR
Registrant Street1:Whois Server:whois.domaindiscover.com
Registrant Street2:Referral URL:www.domaindiscover.com
Registrant City:N/A
Registrant Postal Code:N/A
Registrant Country:CA
Registrant Email:not@available.org
Admin ID:86-C
Admin Name:SEE SPONSORING REGISTRAR
Admin Street1:Whois Server:whois.domaindiscover.com
Admin Street2:Referral URL:www.domaindiscover.com
Admin City:N/A
Admin Postal Code:N/A
Admin Country:CA
Admin Email:not@available.org
Billing ID:86-C
Billing Name:SEE SPONSORING REGISTRAR
Billing Street1:Whois Server:whois.domaindiscover.com
Billing Street2:Referral URL:www.domaindiscover.com
Billing City:N/A
Billing Postal Code:N/A
Billing Country:CA
Billing Email:not@available.org
Tech ID:86-C
Tech Name:SEE SPONSORING REGISTRAR
Tech Street1:Whois Server:whois.domaindiscover.com
Tech Street2:Referral URL:www.domaindiscover.com
Tech City:N/A
Tech Postal Code:N/A
Tech Country:CA
Tech Email:not@available.org
Name Server:NS.MSU.NET
Name Server:NS.MSU.RU
Name Server:NS1.ORC.RU



Found referral to whois.domaindiscover.com.

No match for domain "REISERFS.ORG".

Register your domain today at http://www.domaindiscover.com

evil@prinz:~$

Re: [OT] Re: inode problem?

[Nikita Danilov]

Christian Kujau writes:
 > Nikita Danilov schrieb:
 > >  > {0}:Documentation>host www.reiserfs.org
 > >  > www.reiserfs.org does not exist, try again
 > > 
 > > $ host www.reiserfs.org
 > > www.reiserfs.org has address 212.16.7.65
 > 
 > evil@prinz:~$ host www.reiserfs.org
 > www.reiserfs.org does not exist, try again
 > 
 > > (you can also use namesys.com)
 > 
 > yes, that's what im doing because reiserfs.org.
 > could you tell me your favourite nameserver?

$ nslookup
Default Server:  ns.msu.net
Address:  212.16.0.1

 > 
 > Thanks,
 > Christian.
 > 
 > evil@prinz:~$ whois reiserfs.org
 > NOTICE: Access to .ORG WHOIS information is provided to assist persons

[...]

Nikita.

Re: [OT] Re: inode problem?

[Carl-Daniel Hailfinger]

Christian Kujau wrote:
> evil@prinz:~$ whois reiserfs.org
> NOTICE: Access to .ORG WHOIS information is provided to assist persons
> [...]
> 
> Domain ID:D70636422-LROR
> Domain Name:REISERFS.ORG
> Created On:09-May-2001 17:02:23 UTC
> Last Updated On:09-Jun-2003 21:50:11 UTC
> Expiration Date:09-May-2004 17:02:23 UTC
> Sponsoring Registrar:R86-LROR
> Status:PENDING DELETE
> Status:HOLD

Status PENDING DELETE?

You should better renew the domain before someone else steals it.


Regards,

Carl-Daniel

Re: inode problem?

[burnt_2]

Hans Reiser wrote:

> inodes are yucky yucky.;-) We ain't got none.

So are birthday problems and hash collisions, but I haven't seen you guys address that little detail yet...

(Speaking only as somebody who lost their /usr/local tree to reiserfs.  KEEP BACKUPS, especially if you're using an experimental filesystem.)

--Gordon

Re: inode problem?

[Hans Reiser]

burnt_2@ziplip.com wrote:

>Hans Reiser wrote:
>
>  
>
>>inodes are yucky yucky.;-) We ain't got none.
>>    
>>
>
>So are birthday problems and hash collisions, but I haven't seen you guys address that little detail yet...
>
V4 handles duplicates, and has a larger hash.

>
>(Speaking only as somebody who lost their /usr/local tree to reiserfs.  KEEP BACKUPS, especially if you're using an experimental filesystem.)
>
>
>  
>
Sorry that happened to you.  Were you using a kernel older than 2.4.18? 

-- 
Hans