Re: Bug in mkfs.btrfs?!

[Felix Blanke <felixblanke@gmail.com>]

util-linux-2.18-r1 and still no symlink following.

I'll ask for that at the kernel mailing list in the next days. If your (Hugo)
util-linux doesn't include any kind of patches that behaviour is really strange.


Felix

On 24. January 2011 - 15:44, Felix Blanke wrote:
> Date: Mon, 24 Jan 2011 15:44:14 +0100
> From: Felix Blanke <felixblanke@gmail.com>
> To: Hugo Mills <hugo-lkml@carfax.org.uk>
> Cc: kreijack@inwind.it, linux-btrfs@vger.kernel.org
> Subject: Re: Bug in mkfs.btrfs?!
> 
> > On Mon, Jan 24, 2011 at 02:29:36PM +0000, Hugo Mills wrote:
> > >    If, instead, the initial losetup call tracked the symlinks back to
> > > the original device node (i.e. something like "/dev/sdb3", or
> > > "/dev/mapper/ruthven-btest" in my example), then the name that's
> > > stored in the kernel would be shorter, and we'd be less likely to see
> > > the truncation. This is what my copy of losetup seems to be doing. I
> > > can't see any distribution-specific patches in the source for
> > > util-linux that would do this, though.
> > 
> >    Hmm... Just had a thought: is
> > /dev/disk/by-id/ata-INTEL_SSDSA2M160G2GC_CVPO939201JX160AGN-part3 on
> > your system a symlink or a device node? What does ls -l say?
> 
> It is a symlink created by udev:
> 
> ls -l /dev/disk/by-id/ata-INTEL_SSDSA2M160G2GC_CVPO939201JX160AGN-part3 
> lrwxrwxrwx 1 root root 10 Jan 23 23:39
> /dev/disk/by-id/ata-INTEL_SSDSA2M160G2GC_CVPO939201JX160AGN-part3 -> ../../sdb3
> 
> Following that link should work :)
> 
> 
> Felix
> 
> > 
> >    Hugo.
> > 
> > -- 
> > === 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
> >   --- But people have always eaten people,  / what else is there to ---  
> >          eat?  / If the Juju had meant us not to eat people / he         
> >                      wouldn't have made us of meat.                      
> 
> 
> ---end quoted text---
---end quoted text---