linux-kernel - Re: The ext3 way of journalling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080110144103.GA25187@citd.de>
Date:	Thu, 10 Jan 2008 15:41:03 +0100
From:	Matthias Schniedermeyer <ms@...d.de>
To:	Helge Hafting <helge.hafting@...el.hist.no>
Cc:	Tuomo Valkonen <tuomov@....fi>, linux-kernel@...r.kernel.org
Subject: Re: The ext3 way of journalling

On 10.01.2008 12:30, Helge Hafting wrote:
> Matthias Schniedermeyer wrote:
>>>> Don't use udev then. Good old static dev works fine if you have a fixed
>>>> set of devices.
>>>>       
>>> It doesn't, with the unpredictable SCSI mapping insanity.
>>>     
>>
>> That what LABEL und UUID-Support in mount is for.
>>
>> You label the filesystems (e2label for ext2 and ext3) and use that label to mount them
>>
>> - fstab -
>> LABEL=root  /        xfs     defaults,noatime	0 1
>> LABEL=boot  /boot    ext2    defaults,noatime	0 2
>>   
> Would've been nice if they worked, but they don't.
>
> Disks should be so easy to identify uniquely, because they have
> storage space that can be used for that label.
>
> So I tried (debian linux, last year).
>
> Mount by label was fine, of course.
> Until the 33rd reboot, when it was decided that a
> fsck was necessary "just to be safe".  The problem was that fsck
> fail to find the correct device when /etc/fstab specifies a label
> instead of a device. The boot failed, reboot with init=/bin/sh
> and replace the dysfunctional labels with oldfashioned device names.
>
> I can live with this kind of problem on my desktop, but this machine
> was going to be a internet router for a customer, so occational
> boot failure requiring intervention was not an option.

As written by Theodore somewhere else in this thread support for labels 
in fsck came later, so maybe the fsck-version on your problematic-server 
was too old.

Personally i never had a problem with labels and i use them for about 
4-5 years now.





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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/