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@xxxxxxxxx>
> > To: linux-btrfs@xxxxxxxxxxxxxxx
> > 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:
signature.asc
Description: Digital signature
