From: Hugo Mills <hugo-lkml@carfax.org.uk>
To: Felix Blanke <felixblanke@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Bug in mkfs.btrfs?!
Date: Sat, 22 Jan 2011 15:11:24 +0000 [thread overview]
Message-ID: <20110122151124.GC29985@carfax.org.uk> (raw)
In-Reply-To: <20110122145222.GB2539@scooter>
[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]
On Sat, Jan 22, 2011 at 03:52:22PM +0100, Felix Blanke wrote:
> I was able to create the fs with the --force options. But that bug should be fixed,
> too :)
>
> Is that link maybe too long? It is created by udev, and there was never a problem
> using that link.
Yes, it certainly looks like it. There's 63 characters in the name
in your strace report, so it looks like it's being truncated somewhere.
What was the exact command line you used to get the error?
Hugo.
> Regards,
> Felix
>
> On 22. January 2011 - 15:45, Felix Blanke wrote:
> > Date: Sat, 22 Jan 2011 15:45:13 +0100
> > From: Felix Blanke <felixblanke@gmail.com>
> > To: linux-btrfs@vger.kernel.org
> > Subject: Bug in mkfs.btrfs?!
> >
> > Hi,
> >
> > I wanted to create a new btrfs fs for my backups.
> > When trying to mkfs.btrfs for that device, I'm getting
> >
> > "error checking /dev/loop2 mount status"
> >
> >
> > With strace I see where the problem is:
> >
> > lstat("/dev/disk/by-id/ata-INTEL_SSDSA2M160G2GC_CVPO939201JX160AGN-par",
> > 0x7fffa30b3cf0) = -1 ENOENT (No such file or directory)
> >
> >
> >
> > The problem is there is something missing at the end of the link, should be
> > something like "-part1", "-part2" etc.
> >
> >
> > I'll try the patch with the --foce option.
> >
> > Regards,
> > Felix
> >
> ---end quoted text---
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 515C238D from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Great oxymorons of the world, no. 9: Standard Deviation ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2011-01-22 15:11 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 14:45 Bug in mkfs.btrfs?! Felix Blanke
2011-01-22 14:52 ` Felix Blanke
2011-01-22 15:11 ` Hugo Mills [this message]
2011-01-22 15:45 ` Hugo Mills
2011-01-22 15:56 ` Felix Blanke
2011-01-22 22:54 ` Chris Samuel
2011-01-22 23:03 ` Felix Blanke
2011-01-23 18:18 ` Hugo Mills
2011-01-23 22:02 ` Goffredo Baroncelli
2011-01-23 23:15 ` Felix Blanke
2011-01-24 7:42 ` Helmut Hullen
2011-01-24 9:41 ` Felix Blanke
2011-01-23 23:27 ` Hugo Mills
2011-01-23 23:58 ` Felix Blanke
2011-01-24 1:53 ` Fajar A. Nugraha
2011-01-24 9:38 ` Felix Blanke
2011-01-24 13:01 ` Felix Blanke
2011-01-24 13:13 ` Hugo Mills
2011-01-24 13:53 ` Felix Blanke
2011-01-24 14:29 ` Hugo Mills
2011-01-24 14:34 ` Hugo Mills
2011-01-24 14:44 ` Felix Blanke
2011-01-24 16:52 ` Felix Blanke
2011-01-24 17:00 ` Hugo Mills
2011-01-24 21:04 ` Felix Blanke
2011-01-24 21:14 ` Felix Blanke
2011-01-24 14:35 ` Felix Blanke
2011-01-25 0:15 ` LOOP_GET_STATUS(64) truncates pathnames to 64 chars (was Re: Bug in mkfs.btrfs?!) Chris Samuel
2011-02-10 12:29 ` Petr Uzel
2011-02-11 13:04 ` Felix Blanke
2011-02-11 13:04 ` Felix Blanke
2011-02-11 18:59 ` Milan Broz
[not found] ` <AANLkTi=Arg-09F0DXsWNhsYgyPar=rKs7G_OQG2uMm4f@mail.gmail.com>
2011-02-11 19:31 ` Milan Broz
2011-02-11 19:41 ` Felix Blanke
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=20110122151124.GC29985@carfax.org.uk \
--to=hugo-lkml@carfax.org.uk \
--cc=felixblanke@gmail.com \
--cc=linux-btrfs@vger.kernel.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.