From mboxrd@z Thu Jan  1 00:00:00 1970
From: Felix Blanke <felixblanke@gmail.com>
Subject: Re: Bug in mkfs.btrfs?!
Date: Sat, 22 Jan 2011 15:52:22 +0100
Message-ID: <20110122145222.GB2539@scooter>
References: <20110122144513.GA2539@scooter>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: linux-btrfs@vger.kernel.org
Return-path: <linux-btrfs-owner@vger.kernel.org>
In-Reply-To: <20110122144513.GA2539@scooter>
List-ID: <linux-btrfs.vger.kernel.org>

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.


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---