All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: xfs@oss.sgi.com
Subject: Re: mkfs.xfs doesn't detect size of storage correctly
Date: Thu, 31 Jan 2008 00:26:28 +0100	[thread overview]
Message-ID: <20080130232628.GA9671@citd.de> (raw)
In-Reply-To: <20080129171658.GB21228@citd.de>

A little followup.

Today i bought another 750GB HDD, and a 500GB.

Initializing the encryption of the 500GB finished a minute ago and the 
same bug, of course with a different size (357702MB), was observable.

Workaround also worked in this case (Now its 476937MB). This also proves 
that the bug is of recent nature, the last 500GB HDD i bought was just 
over a month ago and this bug didn't show up then.






Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.

  parent reply	other threads:[~2008-01-30 23:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29  9:32 mkfs.xfs doesn't detect size of storage correctly Matthias Schniedermeyer
2008-01-29 10:15 ` nscott
2008-01-29 12:20   ` Matthias Schniedermeyer
2008-01-29 15:19     ` Eric Sandeen
2008-01-29 15:33       ` Matthias Schniedermeyer
2008-01-29 15:42         ` Eric Sandeen
2008-01-29 16:58           ` Matthias Schniedermeyer
2008-01-29 17:16 ` Matthias Schniedermeyer
2008-01-29 20:14   ` Eric Sandeen
     [not found]     ` <20080129203731.GA29094@puku.stupidest.org>
2008-01-29 21:21       ` Eric Sandeen
2008-01-30 23:26   ` Matthias Schniedermeyer [this message]
2008-01-31  3:17     ` Eric Sandeen
2008-02-05 14:53 ` Eric Sandeen
2008-02-05 15:33   ` Matthias Schniedermeyer
2008-02-05 21:12   ` Mark Goodwin

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=20080130232628.GA9671@citd.de \
    --to=ms@citd.de \
    --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 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.