Re: Strange fs behavior
I think that an fs full situation may occur in your case, have you tried a sleep after the rm? My systems behaves the same, and frequent df displays after the rm of a large file show an increaing amount of freespace. Jan Jaeger From: Ferguson, Neale [EMAIL PROTECTED] Reply-To: Linux on 390 Port [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Strange fs behavior Date: Wed, 11 Sep 2002 08:14:25 -0400 -Original Message- Neale, I do not quite understand what you are saying, when a look at the rexx code i see a loop using various block sizes which: 1) writes to a file (with sufficient real storage, you will write to cache only) In this instance the devices I'm using greatly exceed real memory. 2) sleep for 2 seconds (what happens here? is there an update type sync task running which mignt take control?) I put in a sleep before (and after in a later version) to see if that allowed things to settle down. However, I still get full reports. 3) rm of the file (iirc rm 'syncs' the inode bam blocks asyncronously) 4) sync (which should not do much as the cache has been invalidated) Do you mean to say that you get an fs full after removing the file (ie end round though the loop)? Yes, I get a full condition reported after the remove and dd tries to write its 1st record. Note there's a typo in the exec. It should be: count = (1075 * (4096 / bs.I_bs)) % 1
Re: ls SYS1.PARMLIB or Mainframe FS from Hitachi
Yes. Of cause, I mounted disk under root. And when i executed mount with conv=ebcdik i even can read normal text. Like: sk@zlinux:/mnt/tmp/SYS2.PARMLIB cat CLOCK00 OPERATOR NOPROMPT TIMEZONE E.02.00.00 ETRMODE NO ETRZONE NO ETRDELTA 1 WBR, Sergey Post, Mark K [EMAIL PROTECTED] Sent by: Linux on 390 Port [EMAIL PROTECTED] 12.09.2002 18:54 Please respond to Linux on 390 Port To: [EMAIL PROTECTED] cc: Subject:Re: ls SYS1.PARMLIB or Mainframe FS from Hitachi Sergey, What happens if you try to do this as a non-root user? Can you still see all the files, and display their contents? Mark Post -Original Message- From: Sergey Korzhevsky [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 7:42 AM To: [EMAIL PROTECTED] Subject: ls SYS1.PARMLIB or Mainframe FS from Hitachi Thanks to Motohiro Kanda ! .. WBR, Sergey
Re: Strange fs behavior
Yes, that's what I ended up doing and all is well. -Original Message- I think that an fs full situation may occur in your case, have you tried a sleep after the rm? My systems behaves the same, and frequent df displays after the rm of a large file show an increaing amount of freespace.
CDL/LDL - was Adding a DASD on RedHat 7.2
This discussion has brought CDL to my attention and prompts me to ask which combination of CDL/LDL and partitioning/non-partitioning is recommended. Bob Matthews, University of Geneva. - Original Message - From: Post, Mark K [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 12, 2002 6:55 PM Subject: Re: Adding a DASD on RedHat 7.2 Abel, You need to do one of two things: 1. Run dasdfmt and take the default layout of CDL, and then run fdasd to create at least one partition. 2. Run dasdfmt and specify the Linux layout. Then you can run mke2fs on the volume. Mark Post -Original Message- From: Abdel Gharzita [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 12, 2002 12:41 PM To: [EMAIL PROTECTED] Subject: Adding a DASD on RedHat 7.2 Hi all I am trying to add one full 3380 DASD to increase space on my linux machine, but received the following message when attemp to mke2fs /dev/dasde1 -b 4096: ( I had already formated using dasdfmt -b 4096 -t /dev/dasde and work ok) mke2fs 1.26 (3-Feb-2002) mke2fs: Device size reported to be zero. Invalid partition specified, or partition table wasn't reread after running fdisk, due to a modified partition being busy and in use. You may need to reboot to re-read your partition table. Help! Thanks you! A. Gharzita Pace University DoIT - CSD PS. Is there any admin doc for RedHat Linux for S/390?
