Fargusson.Alan wrote:
> Unless this changed in 2.6 the block devices go through VFS, and the blocks
> get cached by the VFS layer.
>
VFS only comes into play when a filesystem (on a block device) is
mounted. If you access a block device directly (not via a path of the
mountpoint) then VFS is not i
filesystem error switches to ReadOnly
Fargusson.Alan wrote:
> Doing a dd on a device goes through the cache, so in this case the cache
> can't be the problem.
Really?
dd is designed to work on block devices that are not mounted, as well as
files within a mounted filesystem.
I thought t
ECTED] Behalf Of
Carsten Otte
Sent: Friday, August 22, 2008 3:18 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Root filesystem error switches to ReadOnly
Fargusson.Alan wrote:
> Doing a dd on a device goes through the cache, so in this case the cache
> can't be the problem.
This is not t
> I expect the problem is using 'dd' for the copying may not get the
> magic signatures
Also 'dd' expects a dasdfmt'd disks or it loses its way. Another approach
might be to try dasdfmt'ing the disk before 'dd'.
"Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061
---
Rob van der Heij wrote:
I expect the problem is using 'dd' for the copying may not get the
magic signatures that makes the disk a CDL format, so the driver ends
up seeing it as LDL and gets things misaligned. But you should be able
to notice that when the new system is booting.
This is not the c
Fargusson.Alan wrote:
Doing a dd on a device goes through the cache, so in this case the cache can't
be the problem.
This is not the case. In fact, the page cache is indexed by address
spaces and each file as well as each block device has its own address
space. Consequently, Linux cannot tell t
Fargusson.Alan wrote:
> Doing a dd on a device goes through the cache, so in this case the cache
> can't be the problem.
Really?
dd is designed to work on block devices that are not mounted, as well as
files within a mounted filesystem.
I thought the VFS only cached mounted filesystems?
If the
Mark Post wrote:
On 8/21/2008 at 5:22 PM, in message
<[EMAIL PROTECTED]>, Rob van der Heij
<[EMAIL PROTECTED]> wrote:
I expect the problem is using 'dd' for the copying may not get the
magic signatures that makes the disk a CDL format, so the driver ends
up seeing it as LDL and gets things mis
>>> On 8/21/2008 at 5:22 PM, in message
<[EMAIL PROTECTED]>, Rob van der Heij
<[EMAIL PROTECTED]> wrote:
> I expect the problem is using 'dd' for the copying may not get the
> magic signatures that makes the disk a CDL format, so the driver ends
> up seeing it as LDL and gets things misaligned.
I expect the problem is using 'dd' for the copying may not get the
magic signatures that makes the disk a CDL format, so the driver ends
up seeing it as LDL and gets things misaligned. But you should be able
to notice that when the new system is booting.
Have you considered using DDR or such to cop
f Of
Mark Perry
Sent: donderdag 21 augustus 2008 13:27
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Root filesystem error switches to ReadOnly
van Sleeuwen, Berry wrote:
Hello Mark,
I'll have to look into the flashcopy process but have not taken the
time for it just yet.
I guess one thing th
T.EDU
Subject: Re: Root filesystem error switches to ReadOnly
Mark,
Hm, I even didn't think about cache and what it could do to not only
files but also to the filesystem itself. And even if I did I'd have
guessed it would only mess up a logfile that isn't in use on the target
anyway.
Just for a test, try switching the disk references in /etc/fstab to
by-path syntax. I'm speculating here, but is it possible that there are
some issues with correctly identifying which disk to use for /dev/dasda?
--
For LINUX-390
dag 21 augustus 2008 13:27
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Root filesystem error switches to ReadOnly
van Sleeuwen, Berry wrote:
> Hello Mark,
>
> I'll have to look into the flashcopy process but have not taken the
time for it just yet.
>
> I guess one thing that wou
> I guess one thing that would be wrong then is that I copy from the live
system.
I think that's your problem. You're copying from a likely unstable source
(the live system might be writing to your volume as you attempt to copy
it). Try shutting down the master (live) system with "shutdown -h now"
van Sleeuwen, Berry wrote:
> Hello Mark,
>
> I'll have to look into the flashcopy process but have not taken the time for
> it just yet.
>
> I guess one thing that would be wrong then is that I copy from the live
> system. So the source nlzlx920 is being copied from within the nlzlx920. But
> wo
art. It's only within the linux.
Regards, Berry.
-Original Message-
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Perry
Sent: donderdag 21 augustus 2008 12:22
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Root filesystem error switches to ReadOnly
van Sleeuwen, Ber
van Sleeuwen, Berry wrote:
> Hello Mark,
>
> I meant fast in a way that the / is copied and then changes the hostname and
> IP address. No other fancy things, just a default environment for our support
> staff to play around with.
>
> The cloning process is loosly based on the cloning scripts f
Hello Mark,
I meant fast in a way that the / is copied and then changes the hostname and IP
address. No other fancy things, just a default environment for our support
staff to play around with.
The cloning process is loosly based on the cloning scripts from redp4322. The
dasd is copied using D
van Sleeuwen, Berry wrote:
> Hello list,
>
> For various tests we have created a group of new SLES10 guests. They all are
> just one 3390-3 volume so they can be cloned vary fast.
If you use FLASHCOPY its fast regardless of DASD size.
> But for some reason these machines sometimes switch the
Hello list,
For various tests we have created a group of new SLES10 guests. They all are
just one 3390-3 volume so they can be cloned vary fast. But for some reason
these machines sometimes switch the rootdisk, and therefore the entire
filesystem, to readonly. I have tried a remount but that d
21 matches
Mail list logo
