From: Tvrtko Ursulin <tvrtko.ursulin@onelan.co.uk>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Prashant Shah <pshah.mumbai@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: Maximum number of directories
Date: Tue, 05 Feb 2013 14:58:15 +0000 [thread overview]
Message-ID: <3384808.0kkUZK9dS1@deuteros> (raw)
In-Reply-To: <alpine.LFD.2.00.1302051538270.3225@localhost>
On Tuesday 05 February 2013 15:43:51 Lukáš Czerner wrote:
> > > > Yeah, I totally forgot about the inode situation on ext filesystems.
> > > > So is
> > > > tune2fs giving wrong stats for live (mounted) filesystems?
> > >
> > > Not sure what situation you're referring to. Directory as any other
> > > file is represented by an inode and there is a limited number of
> > > inodes in the file system.
> >
> > The situation that inode blocks are statically allocated at mkfs time.
>
> Yes, that is true.
Indeed it is. :)
> > > Using tune2fs on live/mounted file system is bad idea and the
> > > information might not be correct (exactly for this reason it is
> > > _NOT_ recommended to run fsck on live file system). Use 'df -i' if
> > > you want to get information about inode count.
> >
> > Yes, later I figured out that tune2fs -l does not give current stats for
> > live filesystems. I did not expect that to be dangerous though. And I
> > also forgot about 'df -i'. Thing is, I did not hit this limit since the
> > previous century so guess I subconsciously assumed inode limits are an
> > outdated concept. :)
> Running tune2fs -l on live file system is not dangerous, I did not
> said that. Running fsck on live file system on the other hand _is_
> dangerous.
:) Neither have I said I was running fsck or anything other than 'tune2fs -l'.
Regards,
Tvrtko
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-02-05 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 10:55 Maximum number of directories Tvrtko Ursulin
2013-02-04 13:19 ` Prashant Shah
2013-02-04 13:36 ` Tvrtko Ursulin
2013-02-04 15:58 ` Prashant Shah
2013-02-05 13:06 ` Lukáš Czerner
2013-02-05 14:30 ` Tvrtko Ursulin
2013-02-05 14:43 ` Lukáš Czerner
2013-02-05 14:58 ` Tvrtko Ursulin [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=3384808.0kkUZK9dS1@deuteros \
--to=tvrtko.ursulin@onelan.co.uk \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=pshah.mumbai@gmail.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;
as well as URLs for NNTP newsgroup(s).