I have a 500Gb external disk (esata) used a part of a backup cycle. I tried to mount it for the next backup cycle and an i/o error was detected in the ext3 journal. I fixed the bad block but that lost the data in the block and ran fsck.ext3. This resulted in a damaged file system message and a scan of the disk and fsck finished ok. The disk mounts rw. I am not really sure if I should reformat this disk. I have copied the backups off the disk and in any case there are later backups. Reformatting is not a problem but takes time and I would prefer not to do it if it is not required but I want a clean file system
I'm still quite new on linux .. so please accept my question, even if I'm asking something stupid The fact is that I created some months ago a partition of 50 Gb to store my data and I used an ext3 filesystem with journal .. and the journal was about 1 Gb I thinkNow after a few months of usage I moved all my data to a new device and I noticed thapartition was completly emptied, in fact there was still about 10 Gb occupied.All data was moved away, so I think this might be the journal.
Now a few questions:1) Is it normal for a journal to occupy 1/5 of a device? 2) Is there a command or another way to free up the space occupied by the journal?3) Is there a better option in order of filesystem? Maybe it's better to use another one?I usually use ext3 for the system partition and for data storage partition,then I have a partition into where I store clonezilla images for backup purposesand I decided to use reiserfs for it in order to have more space available,even because it's always unmounted and I access onto it only for backup activities
I have a system running CentOS 5.5 (194.32 Kernel) that has been working fine for about 8 months. I found it stuck one morning dumping a Soft Lockup Kernel message every 10 seconds and have been trying to find out what is going on - here is what I've done and found.
System is a Core i3 with 4Gb DDR3 ram and 2 1.5Tb SATA drives - everything is less then 1 year old with not too much load (this is a backup system for my server - a twin and the other works fine)
Intel Mobo: DM55HC
Rebooting the system (after doing a fsck on the drives with lots of errors) it runs for about 20 hours or so and then drops back into this problem.
Prior to going into the soft lockup it reports that the Journal has aborted on one drive or the other and drops into a Read Only FS.
There is nothing in the logs apart from the aborting journal message and the soft-lockup)
Tried fsck with badblocks check on the 2 mountpoints for both drives (dunno how to check the swap partition) - nothing I could see there.
I have tried memtest for about 36hours. No errors
I ran smartctl long tests on both drives. No Errors
I was reading about ext3 feature and I have read about its journaling modes. I would like to ask what is the default journaling mode of ext3 fs in slackware(or is it in all distro using ext3)? I'll install slackware when my new pc arrive and the fs I will use will be ext3 and I like it to have data=journal mode for its journaling. I have read in some wiki how to set the journaling mode into data=journal mode.
Code: # tune2fs -O has_journal -o journal_data /dev/sdXY Do i need to issue this command or is this the default mode in ext3 in slackware?
I have a laptop with important data (no backup) that will not boot. It's a vanilla Debian 6 amd64 with dm-crypt LUKs encryption to a internal sata drive partitioned sda1 sda2 sda5 with lvm2 formatted ext3 for sda5. The symptom is that upon powering up, it progresses (albeit slowly now) past grub, to the point where the the "Enter passphrase" prompt occurs. After entering the phrase, it pauses with "Reading all physical volumes. This may take a while". It seems to work, but then gives me errors like:
ata3.00: status: {DRDY ERR } ata3.00: error: { UNC } ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 ata3.00: BMDMA stat 0x25 ata3.00: failed command READ DMA EXT ...some more stuff... end_request: I/O error:, dev sda, sector 308725410 JBD: Failed to read block at offset 24711 EXT3-fs: error loading journal and it drops me to Busybox ash shell. My impression is that the sda1 partition with the kernel is intact, but the sda2 or sda5 is bad.
What else I have done: 1. Removed problem disk and installed it into another known good laptop. Issue occurs with new laptop. So, I would assume hd is bad, laptop is good. 2. Booted from hd using grub rescue mode. Similar errors occurred. 3. Using suspect laptop and hd, booted into a live cd environment, which attempted to mount the encrypted drive. It prompted for the passphrase, but said it could not mount the drive.
I have installed both Windows Xp and Fedora 12. Last time when i was working on Fedora it didn't shut down properly. Now following error occurs and finally the system sleeps.
ata1.00 : exception Emask 0x0 Sact 0x0 SErr 0x0 action 0x0 ata1.00 : BMDMA stat 0x25 ata1.00 : cmd c8/00:00:50:5a:34/00:00:00:00:00/e4 tag 0 dma 131072 1n res 51/40:7f:d1:5a:34//00:00:00:00:00/e4 Emask 0x9 (media error) ata1.00 : status : { DRDY ERR } ata1.00 : err : { UNC } end_request: I/O error, dev sda, sector 70539985 JBD : Failed to read block at offset 5884 EXT4-fs(sda): error loading journal mount: wrong fs type, bad option, bad superblock on /dev/sda8, codepage or helper program, or other error In some case useful info is found in syslog-ty dmesg | tail or so
I was trying to move my home partition on Ubuntu, and the computer hibernated on me. I restarted it up on the live disk to survey the damage, to find that the home partition, according to fsck, "Superblock has an invalid journal (inode Clear? <y>"
During the file system check of an ext3 partition at boot I get the following output:
The super-block could not be read or does not describe a correct ext2 filesystem. If the device is still valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate super-block:
I'm then forced to login in as root and given the following prompt:
I'm reluctant to do as advised by the output and run e2fsck -b because it is not an ext2 filesystem.
Although I can still enter runlevel 5, it doesn't seem to recognise mouse and keyboard input in KDE so my system is effectively redundant at the mo. For this reason any short term workarounds are welcome, but a fix is needed. This problem is part of a longer saga to do with recovering a Windows Vista installation which started failing to boot. I have used both Vista and SUSE tools to try and recover my bootloader to no avail, and this has been the result. If more detail about this is needed please ask and I can explain what I have done.
After upgrading from opensuse 11.1 to 11.2 I get the following error messages while booting the system caused by the initial filesystem check routines:
ERROR: Couldn't open /dev/null (Too many open files) ext2fs_check_if_mount: Too many open files while determining whether ... is mounted. fsck.ext3: Too many open files while trying to open ...
I found a new version of the e2fsprogs at the OBS package claiming to fix this problem. But installing this new version did not solve my problem.
Here some information about the affected system: Operating System:openSUSE 11.2 (i586) Installed e2fsprogs:e2fsprogs-1.41.11-4.1.i586 Number of LVs:35 (all ext3)
I can only boot if I comment out some of the filesystems in my /etc/fstab. It seems that the number of filesystems must be less or equal 32.
I am trying to install Fedora 11 in Virtual Box using the Live CD. When I try to format with EXT4 (Default) it says the boot volume cannot be EXT4, when I try EXT3 it says it doesn't match the Live filesystem. This is retarded it won't let me use either. (I don't usually throw around the word retarded, only in rare cases and this is one)
I just got a new hard disk so that my "/" and "/home" partitions would be located at their own separate drives. All was well until i tried to expand my "/home" partition to fill up the entire drive that used to also have the "/" and swap partitions on there. Let me sketch the before-and-after scenario in GParted,
Before:
What actually happened after:
Gparted gave an error prompt after which i found out that the entire ext3 partition (/home) had been moved to the left but not yet expanded to the right, which is of course not a problem. However, for some reason it has labelled the entire ext3 partition as a swap partition!
I'm still running ubuntu from the usb flash drive, because i dont want to risk that the (120GB) swap area will actually be used and cause my data to be lost.
I guess my question is, can i relabel the swap partition as ext3 like it was before without formatting (ie without losing data)?
Here's the output of "fdisk -l", which doesn't show the swap area (the drive in question is "/dev/sdb"):
End_request: I/O error, dev sds, sector 420656157 EXT3-fs error (device sda2) : ext3_find_entry : reading directory # 52527153 offset What is this Above Error which I am getting , on my server
I am trying to figure out a totally odd behavior of the ext3 filesystem mounted in Ubuntu 9.10. There is a Korn Shell script, part of which does the following in the loop:
while ((1)); do mv dir1/file dir2; if [[ ! -r dir2/file ]]; then echo "ERROR" ls -l dir1/* dir2/* exit 1 elif echo "OK" fi done
Given that dir2/file always exists and that I do not move it asynchronously with "&", my script should never hit the "ERROR" statement. The odd thing is that it does, and quite randomly (no pattern at all). However when it does hit the ERROR case, ls -l prints that file is in dir2 and it is readable! I tried using "-e" instead of "-r" test - no luck. I never seen anything like this in 10 years of my programming experience. Same script worked fine on Fedora 11, and yet it wouldn't work on Ubuntu.
I am using Wind River Linux- 2.6.27.18-WR3.0bg_standard. The problem is whenever I execute "reboot, ls, cd" and many other commands the OS prompts me an error- "end request: i/o error, dev sda, sector "(different sector each time)" and EXT3-fs error (device sda1):ext3_get_inode_loc:unable to read inode block- inode-4088001, block-4097027 I also executed "dmesg", it also showed similar errors. Has the disk gone bad or the kernel is corrupted?
I Tarred and GZipped most of the data on one 1Tb partition and stuck the archives on a second 1Tb partition on a separate disk. I then proceeded to format the first partition with NTFS (from Linux.) The only problem is that I completely forgot that I had a CD drive and formatted sdc1 instead of sdd1! I began doing a full NTFS format and after a minute or two I cancelled it and decided to do a quick format. I then realized my mistake. I managed to find a copy of the superblock and began trying to recover the disk. fsck -t ext3 recognized the partition as NTFS but I luckily didn't have fsck.ntfs installed so it didn't touch it. I managed to get it working with fsck.ext3 (with -b,-B and -y) fsck.ext3 didn't mind that it was an NTFS partition.
Roughly how long will this take? It's running from Knoppix within a virtual machine to a USB hard drive which is 100% full. Days? Being that for a few minutes I attempted a full format am I going to end up with a bunch of corrupted archives? If I do end up with file corruption can anyone recommend a way of recovering the data / sorting it out? Is it likely to be just a few old files that are corrupt (It's my understanding that filesystems like to keep files in the same area on the disk to minimize the amount of head travel.) This might just be wishful thinking but as the filesystem fills up will ext3 put the newer files towards the end of the disk? If so then I'm hoping that a full NTFS format starts at the beginning of the disk.
I have a problem partitioning an Hard Disk Drive on a server, and I hope someone can help me with this. Here is the system configuration: Operating System Linux localhost.localdomain 2.6.30.8-64.fc11.x86_64 #1 SMP Fri Sep 25 04:43:32 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
Hardware: RAID bus controller: Hewlett-Packard Company Smart Array G6 controllers (rev 01)
The system mounts one hard disk (120 Gb) with the OS, and four 1.5Tb Hard Disks mounted on RAID 10 for a total of ~3 Tb I need to create several partitions on this RAID drive, but I have some trouble doing it. I need a total of 10 partitions of different sizes:
I would like to see the journal of a file-system (ex. ext4) in action. What i mean is that, without knowing what kind of fs is on a partition, i want to test if this fs supports or not journaling.
I have an 80 GB XFS / partition which is dying. Got some errors like this: ata9: SError: { UnrecovData Dispar BadCRC Handshk }
It's not a problem to create another partition, I've got 2 500GB and 2 1TB disks, all EXT3. I've also 2 80 GB disks, 1 for / and 1 for /home. I will remove the 2 80 GB disks but I have a lot of stuff compiled myself. I use openSUSE 11.1. Is it possible to create a 80 GB EXT3 partition on each of the 500 GB hdd, 1 for / and 1 for /home and move the data to it? must it be done with the DD command or can I easily copy everything within a live-cd. The /boot and swap are already on one of the 500GB disks, and there is no bootrecord on the 80 GB disks.
I want to install the Zeitgeist Activity Journal on Fedora 12, there is a package zeitgeist-0.3.2-1.fc12 (noarch) in the repos and the description says its just the daemon without user interface/gui.
How can I use it on F12, there are many Screenshots on the Internet like this one:
[url] [url]
I want it as shown in the picture and not in combination with gnome shell. What do I have to install ?
I have a Westel 1 TB external hard drive and when attempting to partition it, the partitioner never finishes refreshing the device. I've tried gparted live, opensuse, & ubuntu; and none of them finish refreshing the device.
Another issue is, I have 200 gig of music & movies that can't be wiped out because I got no room elsewhere to move them to. I would like to set a partition of 750 gig for the ext 3 and leave the rest for ntfs.
I would like to adjust the journal program called lifeograph. First I would like to build it, clean without any adjustments.
I'm using this version: [URL]
Readme file says:
Requirements ----------- Lifeograph requires the following modules to be built: * gtkmm, * gconfmm, * gtkspell, and * gcrypt. Installation ------------
Type "make" to build and "make install" to install (all without quotes). No configuration atm.
I tried make, but it doenst really work. So i think i dont have good requirements.
-> how do I install the required modules? -> I've found some in packet manager, but some appear to be librarys.
I'm on 10.04 64-bit and can't get tagging to work in Activity Journal (.5) or Tracker (., installed from the ppas. Am I missing something? It'd be really nice to have tag-level access in addition to hierarchal directories! I've spent two hours past my bedtime working on this and am stumped.
Whenever I try opening the Gnome Activity Journal from Applications > Accessories > Gnome Activity Journal, it doesn't open, nothing shows up, and not even in the System Monitor. So I took a different route, by opening it from the Terminal, to see if it gave me anything, and when I type in 'gnome-activity-journal' it spits this out at me:
since switching from Windows, I have been using Lifeograph, which is a neat little program.
However, my needs are such now, that I am in need of something portable and cross-platform capable, for a whole bunch of reasons.
Basically, I need something that does the job of Lifeograph, or David RM's The Journal, but it needs to be useable from a USB stick in both Windows and Linux.
I know it seems I want the moon on a stick, but i have my reasons. It does not have to be free/open source either. I am happy to pay, so long as it does the job.
