* [gentoo-user] fsck and mount by label
@ 2011-07-30 9:42 Florian Philipp
2011-07-30 14:01 ` Michael Mol
2011-07-30 19:37 ` [gentoo-user] " Nikos Chantziaras
0 siblings, 2 replies; 6+ messages in thread
From: Florian Philipp @ 2011-07-30 9:42 UTC (permalink / raw
To: Gentoo User List
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
Hello list!
I've noticed the following in my rc.log file:
[file system mounting ...]
opt: clean, 3127/6496 files, 108510/209920 blocks
fsck.ext4: Unable to resolve »LABEL=backup«
* Operational error
The backup disk is the only one (besides boot and root) which is mounted
by label. After booting, I find that the backup disk was mounted
correctly. If I then try to run
`fsck.ext4 "LABEL=backup"`, it works as expected.
Does anyone have an explanation for this?
Thanks in advance!
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] fsck and mount by label
2011-07-30 9:42 [gentoo-user] fsck and mount by label Florian Philipp
@ 2011-07-30 14:01 ` Michael Mol
2011-07-31 9:06 ` Florian Philipp
2011-07-30 19:37 ` [gentoo-user] " Nikos Chantziaras
1 sibling, 1 reply; 6+ messages in thread
From: Michael Mol @ 2011-07-30 14:01 UTC (permalink / raw
To: gentoo-user
On Sat, Jul 30, 2011 at 5:42 AM, Florian Philipp <lists@binarywings.net> wrote:
> Hello list!
>
> I've noticed the following in my rc.log file:
> [file system mounting ...]
> opt: clean, 3127/6496 files, 108510/209920 blocks
> fsck.ext4: Unable to resolve »LABEL=backup«
> * Operational error
>
> The backup disk is the only one (besides boot and root) which is mounted
> by label. After booting, I find that the backup disk was mounted
> correctly. If I then try to run
> `fsck.ext4 "LABEL=backup"`, it works as expected.
>
> Does anyone have an explanation for this?
Could it be that the volume 'backup' is on isn't available yet? (i.e.
brought up by lvm later in the boot process)
--
:wq
^ permalink raw reply [flat|nested] 6+ messages in thread
* [gentoo-user] Re: fsck and mount by label
2011-07-30 9:42 [gentoo-user] fsck and mount by label Florian Philipp
2011-07-30 14:01 ` Michael Mol
@ 2011-07-30 19:37 ` Nikos Chantziaras
2011-07-31 9:06 ` Florian Philipp
1 sibling, 1 reply; 6+ messages in thread
From: Nikos Chantziaras @ 2011-07-30 19:37 UTC (permalink / raw
To: gentoo-user
On 07/30/2011 12:42 PM, Florian Philipp wrote:
> Hello list!
>
> I've noticed the following in my rc.log file:
> [file system mounting ...]
> opt: clean, 3127/6496 files, 108510/209920 blocks
> fsck.ext4: Unable to resolve »LABEL=backup«
> * Operational error
>
> The backup disk is the only one (besides boot and root) which is mounted
> by label. After booting, I find that the backup disk was mounted
> correctly. If I then try to run
> `fsck.ext4 "LABEL=backup"`, it works as expected.
>
> Does anyone have an explanation for this?
I had similar problems, but I never understood what's causing them. I
solved it by using "/dev/disk/by-label/backup" instead of "LABEL=backup".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] fsck and mount by label
2011-07-30 14:01 ` Michael Mol
@ 2011-07-31 9:06 ` Florian Philipp
2011-07-31 13:04 ` Michael Mol
0 siblings, 1 reply; 6+ messages in thread
From: Florian Philipp @ 2011-07-31 9:06 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
Am 30.07.2011 16:01, schrieb Michael Mol:
> On Sat, Jul 30, 2011 at 5:42 AM, Florian Philipp <lists@binarywings.net> wrote:
>> Hello list!
>>
>> I've noticed the following in my rc.log file:
>> [file system mounting ...]
>> opt: clean, 3127/6496 files, 108510/209920 blocks
>> fsck.ext4: Unable to resolve »LABEL=backup«
>> * Operational error
>>
>> The backup disk is the only one (besides boot and root) which is mounted
>> by label. After booting, I find that the backup disk was mounted
>> correctly. If I then try to run
>> `fsck.ext4 "LABEL=backup"`, it works as expected.
>>
>> Does anyone have an explanation for this?
>
> Could it be that the volume 'backup' is on isn't available yet? (i.e.
> brought up by lvm later in the boot process)
>
I thought of this, as well, especially because it is a firewire disk.
But then why is it mounted correctly?
Regards,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] Re: fsck and mount by label
2011-07-30 19:37 ` [gentoo-user] " Nikos Chantziaras
@ 2011-07-31 9:06 ` Florian Philipp
0 siblings, 0 replies; 6+ messages in thread
From: Florian Philipp @ 2011-07-31 9:06 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
Am 30.07.2011 21:37, schrieb Nikos Chantziaras:
> On 07/30/2011 12:42 PM, Florian Philipp wrote:
>> Hello list!
>>
>> I've noticed the following in my rc.log file:
>> [file system mounting ...]
>> opt: clean, 3127/6496 files, 108510/209920 blocks
>> fsck.ext4: Unable to resolve »LABEL=backup«
>> * Operational error
>>
>> The backup disk is the only one (besides boot and root) which is mounted
>> by label. After booting, I find that the backup disk was mounted
>> correctly. If I then try to run
>> `fsck.ext4 "LABEL=backup"`, it works as expected.
>>
>> Does anyone have an explanation for this?
>
> I had similar problems, but I never understood what's causing them. I
> solved it by using "/dev/disk/by-label/backup" instead of "LABEL=backup".
>
>
Interesting. I think I'll try it.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-user] fsck and mount by label
2011-07-31 9:06 ` Florian Philipp
@ 2011-07-31 13:04 ` Michael Mol
0 siblings, 0 replies; 6+ messages in thread
From: Michael Mol @ 2011-07-31 13:04 UTC (permalink / raw
To: gentoo-user
On Sun, Jul 31, 2011 at 5:06 AM, Florian Philipp <lists@binarywings.net> wrote:
> Am 30.07.2011 16:01, schrieb Michael Mol:
>> On Sat, Jul 30, 2011 at 5:42 AM, Florian Philipp <lists@binarywings.net> wrote:
>>> Hello list!
>>>
>>> I've noticed the following in my rc.log file:
>>> [file system mounting ...]
>>> opt: clean, 3127/6496 files, 108510/209920 blocks
>>> fsck.ext4: Unable to resolve »LABEL=backup«
>>> * Operational error
>>>
>>> The backup disk is the only one (besides boot and root) which is mounted
>>> by label. After booting, I find that the backup disk was mounted
>>> correctly. If I then try to run
>>> `fsck.ext4 "LABEL=backup"`, it works as expected.
>>>
>>> Does anyone have an explanation for this?
>>
>> Could it be that the volume 'backup' is on isn't available yet? (i.e.
>> brought up by lvm later in the boot process)
>>
>
> I thought of this, as well, especially because it is a firewire disk.
> But then why is it mounted correctly?
It might be brought up by an automounter later on. You might try
removing the entry from fstab, and see if it still gets mounted.
--
:wq
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2011-07-31 13:06 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-30 9:42 [gentoo-user] fsck and mount by label Florian Philipp
2011-07-30 14:01 ` Michael Mol
2011-07-31 9:06 ` Florian Philipp
2011-07-31 13:04 ` Michael Mol
2011-07-30 19:37 ` [gentoo-user] " Nikos Chantziaras
2011-07-31 9:06 ` Florian Philipp
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox