All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@nokia.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: "Bityutskiy Artem \(Nokia-D/Helsinki\)"
	<Artem.Bityutskiy@nokia.com>,
	linux-mtd Mailing List <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS warning: ubifs_vm_page_mkwrite: out of space for mmapped file
Date: Fri, 18 Sep 2009 10:56:34 +0300	[thread overview]
Message-ID: <4AB33D32.8070109@nokia.com> (raw)
In-Reply-To: <9c9fda240909180026x7183ccecw9a1a3430090787a3@mail.gmail.com>

Kyungmin Park wrote:
> Hi,
> 
> Do you have any clue of following message?
> 
> We used the latest UBIFS.
> 
> [21474583.825000] UBIFS warning (pid 1263): ubifs_vm_page_mkwrite: out
> of space for mmapped file (inode number 2180)
> [21474583.830000] UBIFS warning (pid 1263): ubifs_vm_page_mkwrite: out
> of space for mmapped file (inode number 2180)
> [21474584.190000] UBIFS warning (pid 1362): ubifs_vm_page_mkwrite: out
> of space for mmapped file (inode number 2180)
> [21474584.200000] UBIFS warning (pid 1362): ubifs_vm_page_mkwrite: out
> of space for mmapped file (inode number 2180)

Unlike a block-based file system, in UBIFS if you mmap a file and write to it, 
you can run out of space.

(Actually you can also run out of space on a block-based file system that
implements sparse files and you write into a hole)

  reply	other threads:[~2009-09-18  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18  7:26 UBIFS warning: ubifs_vm_page_mkwrite: out of space for mmapped file Kyungmin Park
2009-09-18  7:56 ` Adrian Hunter [this message]
2009-09-19  1:34   ` Kyungmin Park

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=4AB33D32.8070109@nokia.com \
    --to=adrian.hunter@nokia.com \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=kmpark@infradead.org \
    --cc=linux-mtd@lists.infradead.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 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.