On 2019-08-10, Dennis Wicks wrote:
>
> If you have some suggestions on what info to gather then let
> me know. Bear in mind that during the boot process my system
> is pretty much unresponsive for the hour or so until the
> window manager is up and everything has settled down.
>
An hour or
Greetings once again;
Tomorrow morning I am going to reboot and see if my problem
happens again.
If you have some suggestions on what info to gather then let
me know. Bear in mind that during the boot process my system
is pretty much unresponsive for the hour or so until the
window manager
David Wright wrote on 8/8/19 9:04 AM:
On Thu 08 Aug 2019 at 08:19:22 (-), Curt wrote:
On 2019-08-05, Dennis Wicks wrote:
So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
seemed to finish successfully, but "ls /wa1" indicated that
in fact it had not. Nothing mounted on wa1! Many
Curt wrote on 8/8/19 3:41 AM:
On 2019-08-08, Curt wrote:
On 2019-08-05, Dennis Wicks wrote:
So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
seemed to finish successfully, but "ls /wa1" indicated that
in fact it had not. Nothing mounted on wa1! Many other tests
told me the same
Curt wrote on 8/8/19 3:19 AM:
On 2019-08-05, Dennis Wicks wrote:
So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
seemed to finish successfully, but "ls /wa1" indicated that
in fact it had not. Nothing mounted on wa1! Many other tests
told me the same thing. "umount /wa1" said "not
Hi,
David Wright wrote:
> it appears that any subsequent mount commands have to
> agree explicitly with the earlier choice. Are there other, similar
> factors involved in the OP's case…
Ah yes.
I was similarly confused by my system's behavior on double mount
and the fact that i remember to have
On Fri, Aug 09, 2019 at 11:29:17AM -0500, David Wright wrote:
> Whether I like the ability to mount in this manner, I'm with Greg at the
> moment. Obviously I missed any discussion on the topic ~15 years ago,
> so I haven't seen any benefits spelled out. In any case, perhaps a
> warning in
Sorry to cause the thread to "wander", but some of us are trying to
replicate aspects of the OP's problem, which necessitates explaining
any differences in the results being obtained.
On Thu 08 Aug 2019 at 14:14:25 (-0400), Michael Stone wrote:
> On Thu, Aug 08, 2019 at 12:09:11PM -0500, David
On Thu, Aug 08, 2019 at 12:09:11PM -0500, David Wright wrote:
On Thu 08 Aug 2019 at 10:56:46 (-0400), Michael Stone wrote:
On Thu, Aug 08, 2019 at 09:04:00AM -0500, David Wright wrote:
> wren 08:50:11 ~# lsblk -f | grep sda7
> ├─sda7 ext4swan07
On Thu, Aug 08, 2019 at 12:09:11PM -0500, David Wright wrote:
> But the 2-1 vote wasn't whether error messages were emitted, but
> whether the system should mount an already-mounted partition onto
> another mount point. I get error messages and the mount fails.
> Others get no error messages
On Thu 08 Aug 2019 at 10:56:46 (-0400), Michael Stone wrote:
> On Thu, Aug 08, 2019 at 09:04:00AM -0500, David Wright wrote:
> > wren 08:50:11 ~# lsblk -f | grep sda7
> > ├─sda7 ext4swan07 4a4e352f-2180-4083-92b4-f46e4e0104b4
> > /wrenbk
> > wren 08:50:26 ~# mkdir /wa1
On Thu, Aug 08, 2019 at 09:04:00AM -0500, David Wright wrote:
wren 08:50:11 ~# lsblk -f | grep sda7
├─sda7 ext4swan07 4a4e352f-2180-4083-92b4-f46e4e0104b4
/wrenbk
wren 08:50:26 ~# mkdir /wa1 /somethingelse
wren 08:50:49 ~# mount /dev/sda7 /somethingelse
mount: /dev/sda7 is
On Thu 08 Aug 2019 at 08:19:22 (-), Curt wrote:
> On 2019-08-05, Dennis Wicks wrote:
> > So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
> > seemed to finish successfully, but "ls /wa1" indicated that
> > in fact it had not. Nothing mounted on wa1! Many other tests
> > told me the
On 2019-08-08, Michael Stone wrote:
> On Thu, Aug 08, 2019 at 11:52:41AM +0200, Thomas Schmitt wrote:
>>The central riddle is how mount(8) can fail to make the filesystem
>>available without visibly reporting an error.
>>A question about "mount -v" and its exit value is pending.
>>Maybe one
On Thu, Aug 08, 2019 at 11:52:41AM +0200, Thomas Schmitt wrote:
The central riddle is how mount(8) can fail to make the filesystem
available without visibly reporting an error.
A question about "mount -v" and its exit value is pending.
Maybe one should also look at dmesg output after such a
On 2019-08-08, Thomas Schmitt wrote:
> Hi,
>
> The central riddle is how mount(8) can fail to make the filesystem
> available without visibly reporting an error.
Nothing to do with these swaps spaces (I took a gander at the /etc/fstab)?
/wa1/Swap5 ...
/wa2/Swap6 ...
"I can
Hi,
Curt wrote:
> Did you show your /etc/fstab file (cut and paste)? If so, I must've missed
> it.
See https://lists.debian.org/debian-user/2019/08/msg00295.html
where the attachments are kindly attached to the body text.
Results from "mount" without arguments or the contents of /etc/mtab
and
On 2019-08-08, Curt wrote:
> On 2019-08-05, Dennis Wicks wrote:
>>
>>
>> So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
>> seemed to finish successfully, but "ls /wa1" indicated that
>> in fact it had not. Nothing mounted on wa1! Many other tests
>> told me the same thing. "umount
On 2019-08-05, Dennis Wicks wrote:
>
>
> So anyway, I typed in "sudo mount /dev/sdb2 /wa1" and it
> seemed to finish successfully, but "ls /wa1" indicated that
> in fact it had not. Nothing mounted on wa1! Many other tests
> told me the same thing. "umount /wa1" said "not mounted"!
Would this
Hi,
i wrote:
> >mount -v /dev/sdc /wa1
> >echo $?
Duh. "/dev/sdb2", not "/dev/sdc".
(Do as i mean, not as i write.)
Dennis Wicks wrote:
> I'll put a note in my fstab so the next time I boot I can find it if the
> mount fails again!
Did i miss the report about some miracle cure beyond
On Wed 07 Aug 2019 at 12:44:39 (-0500), Dennis Wicks wrote:
> David Wright wrote on 8/6/19 1:48 PM:
> > On Tue 06 Aug 2019 at 12:18:21 (-0500), Dennis Wicks wrote:
> > > Thomas Schmitt wrote on 8/6/19 10:30 AM:
> > > > Dennis Wicks wrote:
> > > > > I *cannot* mount *any* partition on /wa1
> > > >
On Wed, Aug 07, 2019 at 12:44:39PM -0500, Dennis Wicks wrote:
> And the
> system does not object or give an error when you mount the same partition on
> two diff dirs anyway!
Sadly. And *very* surprisingly. You can only wish that it did.
Thomas Schmitt wrote on 8/6/19 1:58 PM:
Hi,
more ideas: exit value, verbous mode.
mount -v /dev/sdc /wa1
echo $?
A nominally successful mount command would yield 0 as "$?".
Maybe -v yields some extra insight.
Have a nice day :)
Thomas
Thanks, Thomas!
I'll put a note in my fstab
David Wright wrote on 8/6/19 1:48 PM:
On Tue 06 Aug 2019 at 12:18:21 (-0500), Dennis Wicks wrote:
Thomas Schmitt wrote on 8/6/19 10:30 AM:
Dennis Wicks wrote:
I *cannot* mount *any* partition on /wa1
but I *can* mount *any* partition on any other mount point.
So what do you get from these
Hi,
more ideas: exit value, verbous mode.
mount -v /dev/sdc /wa1
echo $?
A nominally successful mount command would yield 0 as "$?".
Maybe -v yields some extra insight.
Have a nice day :)
Thomas
On Tue 06 Aug 2019 at 12:18:21 (-0500), Dennis Wicks wrote:
> Thomas Schmitt wrote on 8/6/19 10:30 AM:
> > Dennis Wicks wrote:
> > > I *cannot* mount *any* partition on /wa1
> > > but I *can* mount *any* partition on any other mount point.
> >
> > So what do you get from these shell commands ?
>
On 7/08/19 5:51 AM, Dennis Wicks wrote:
> Richard Hector wrote on 8/6/19 12:42 PM:
>> On 7/08/19 5:31 AM, Dennis Wicks wrote:
>>> rhkra...@gmail.com wrote on 8/6/19 10:34 AM:
I didn't fully understand your fstab, but is there a typo -- wa11 vs.
wa1?
>>> No. My current config is;
>>>
>>>
Richard Hector wrote on 8/6/19 12:42 PM:
On 7/08/19 5:31 AM, Dennis Wicks wrote:
rhkra...@gmail.com wrote on 8/6/19 10:34 AM:
I didn't fully understand your fstab, but is there a typo -- wa11 vs.
wa1?
No. My current config is;
/wa1 -> wa11 ( soft link )
/wa11 ( <- /dev/sdb2 )
On 7/08/19 5:31 AM, Dennis Wicks wrote:
> rhkra...@gmail.com wrote on 8/6/19 10:34 AM:
>> I didn't fully understand your fstab, but is there a typo -- wa11 vs.
>> wa1?
> No. My current config is;
>
> /wa1 -> wa11 ( soft link )
> /wa11 ( <- /dev/sdb2 )
>
> with sdb2 mounted on /wa11
rhkra...@gmail.com wrote on 8/6/19 10:34 AM:
I didn't fully understand your fstab, but is there a typo -- wa11 vs. wa1?
No. My current config is;
/wa1 -> wa11 ( soft link )
/wa11( <- /dev/sdb2 )
with sdb2 mounted on /wa11 so I don't have to find and
change all the paths that I
Felix Miata wrote on 8/6/19 10:33 AM:
Dennis Wicks composed on 2019-08-06 10:09 (UTC-0500):
I *cannot* mount *any* partition on /wa1
What is output from ls -ld /wa*/ ?
wix@dgwicks:/$ ls -ld /wa*/
drwxrwxrwx 17 root root 4096 Jun 17 14:07 /wa1/
drwxrwxrwx 17 root root 4096 Jun 17 14:07
Thomas Schmitt wrote on 8/6/19 10:30 AM:
Hi,
Dennis Wicks wrote:
I *cannot* mount *any* partition on /wa1
but I *can* mount *any* partition on any other mount point.
So what do you get from these shell commands ?
I am currently running with "ln -s /wa11 /wa1" so this isn't
the config I
I didn't fully understand your fstab, but is there a typo -- wa11 vs. wa1?
On Tuesday, August 06, 2019 11:09:32 AM Dennis Wicks wrote:
> Requested info attached:
>
> I *cannot* mount *any* partition on /wa1
> but I *can* mount *any* partition on any other mount point.
>
> Regards, and Thanks!
>
Dennis Wicks composed on 2019-08-06 10:09 (UTC-0500):
> I *cannot* mount *any* partition on /wa1
What is output from ls -ld /wa*/ ?
--
Evolution as taught in public schools is religion, not science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Hi,
Dennis Wicks wrote:
> I *cannot* mount *any* partition on /wa1
> but I *can* mount *any* partition on any other mount point.
So what do you get from these shell commands ?
ls -ld /wa1 /wa11
find /wa1
What happens if you create a new /wa1 ?
mv /wa1 /wa1_old
mkdir /wa1
mount
Requested info attached:
I *cannot* mount *any* partition on /wa1
but I *can* mount *any* partition on any other mount point.
Regards, and Thanks!
Dennis
Andrei POPESCU wrote on 8/6/19 1:06 AM:
On Lu, 05 aug 19, 15:33:57, Dennis Wicks wrote:
It seems that something in the mount process does
On Lu, 05 aug 19, 15:33:57, Dennis Wicks wrote:
>
> It seems that something in the mount process does not like "wa1" for a mount
> point. Anybody have similar recent problems?
Please show your fstab and the output of 'lsblk -f'.
Kind regards,
Andrei
--
I recently rebooted after an upgrade that generated
"Jul 28 17:13 initrd.img-4.19.0-5-686-pae"
and when I was finally U I discovered that a mount didn't
happen. (I am on Debian 10 Bullseye and my last kernel
resulted in "Jul 18 17:23 vmlinuz-4.19.0-5-686-pae".)
I have mount points
38 matches
Mail list logo
