similar to: E2fsck and large file

Has anyone tried LFS (ie >2G files support) and Ext3 together? Are there good reasons why this should/should not work? I see the RH enterprise kernel patch set specifically does not attempt both lfs and ext3, but the lfs patches themselves touch some reasonably localised parts of ext2, so I would hope (without having dived in there to test), that the ext3 changes would mirror that

hi, i have a tricky situation here and and don't know where to start with the solution. i happened to set up a linux system, but i had to install the base system on another machine. i used e2fsprogs 1.30-WIP (30-Sep-2002) for this. now the machine is up and running, but i have to use e2fsprogs 1.27 (8-Mar-2002). it's a debian system and i wanted to stay sane & stable, hence using

Looks like virt-v2v cannot be built now, since it requires non-existing version of libguestfs-devel. Based on (no README or any instructions in virt-v2v) http://libguestfs.org/guestfs-building.1.html I tried this: git clean -dxf ./autogen.sh And it fails with: --- Checking for libraries used by virt-v2v --- checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version

Dear R-helpers, I am using the package "gee" to run a marginal model. Here is the output. In my simulated data, both x and z are time-varying, so I include their interaction terms with time indicator (i.e. tind=0, if time 1, and 1 if time 2) The data is simulated, so the true parameter of z both at time 1 and time 2 is 5, which is very close from the model output for time 1, z =

With kernel 2.6.30-rc2-git6 and prior I am having problems mounting ext4 partitions after reboot. A successful mount looks like this: /dev/cciss/c0d0p8 on /squid-cache0 type ext4 (rw,noexec,nodev,noatime,data=writeback,errors=panic) /dev/cciss/c0d0p9 on /squid-cache1 type ext4 (rw,noexec,nodev,noatime,data=writeback,errors=panic) /dev/cciss/c0d0p10 on /squid-data type ext4

I'm impressed that I was able to whip this out in just one day of hacking. Below, I'll include a diff between the plugin and the filter as of patch 1, if it aids review. Eric Blake (3): filters: Add ext2 filter ext2: Deprecate ext2 plugin ext2: Add mode for letting client exportname choose file from image TODO | 5 - configure.ac

Other than what is printed on STD{OUT|ERR}, is there any functional difference between the -p and -y arguments in the e2fsck command? ..Chuck.. -- Chuck Wolber Electronic Flight Bag/ Network File Server Crew Information Systems/ OSS Wonk Mobile: 253.576.1154 Desk: 206.655.6918 "21. A person who is nice to you, but rude to the waiter, is not a nice person." -Dave Barry "25 things

Hi! I had problem yesterday with e2fsck. It reported a bad superblock. I then tried to use one of the other superblocks. To no avail. Then later I remembered that I had switched the fs type to xfs. Maybe e2fsck could recognize other common fs types, and report this instead? best regards keld

Helping a friend fix a computer that was having severe, weird troubles. Reformatted (from XP) and installed Fedora. Install went ok, on first boot, however, filesystem was READONLY for some reason. Knew hard drive was suspect, so I e2fsck'd it over and over all night long, fall asleep next to the computer. This morning, Fedora boots fine, login not a problem, so I shut down and fsck it again,

hi, just wanted to mention that using 1.36-rc1 fixes the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=144771 thanks to benjamin scott for the hint, and theodore ts'o for fixing. building a source and binary rpm with the provided spec file works flawlessly under fc3 (just had to remove -rc1 from the archive name and Version: in the spec file). if you are replying to

Hi, It seems one of my computers died last night and it looks like hard disk trouble. I took the disk out and attached to another system and tried to mount the partition, but the mount doesn't complete and just hangs (process is also unkillable - I had to reboot). So, I tried to run "fsck -fccp /dev/sda2" but the command just hangs after printing "/dev/sda2: recovering

I've run ext3 filesystems for the last few years and I've never seen this question answered..... If a system shutsdown hard, even with journaling is it at all necessary to run e2fsck? Just curious.... Thanks -- Sam Williams samurai at acm.org +----------------------------------------------------------------------+ +"It is easy to be

I have a bit of a problem with the machine I use at home for backups. The main partition the backups reside on is a 4 disk RAID-5, totaling around 240GB. This has had some sort of corruption inflicted on it, in the content of the (at least) one directory, where there are now corrupted directory entries. This happened after I added an additional SiS PCI IDE controller card to the machine and put

fsck (Red Hat Enterprise Linux AS 2.1) returns an exit code 127 on an ext3 file system when run from a shellscript started by cron. Here is the pertinent part of the script: ... fsck -p /dev/${BK_SLICE} 1>/dev/null 2>&1 STATUS=$? if [ ${STATUS} -ne "0" ] then echo "${MIR_PID}: file system check of /dev/${BK_SLICE} failed, status = ${STATUS}" >>${LOG}

Hi, just to do nothing wrong: for lustre 1.6.0.1 e2fsprogs version: 1.39.cfs8 is recommended. Can I assume that I can also better use the most recent version which is recommended for 1.6.4.1 which is e2fsprogs version: 1.40.2-cfs1 Harald -- Harald van Pee Helmholtz-Institut fuer Strahlen- und Kernphysik der Universitaet Bonn

Use commandrvf() instead of commandvf() to execute e2fsck. A non-zero exit status does not always indicate a failure. Signed-off-by: Nikos Skalkotos <skalkoto@grnet.gr> --- daemon/ext2.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/daemon/ext2.c b/daemon/ext2.c index 65ddae6..8ef6d5f 100644 --- a/daemon/ext2.c +++ b/daemon/ext2.c @@ -296,9 +296,9 @@ do_e2fsck

On Sun, Jun 01, 2014 at 07:43:12PM -0700, Keith Keller wrote: > > That's clearly a spurious error, so I checked dmesg: > > [159891.225762] EXT4-fs (dm-0): get root inode failed > [159891.227436] EXT4-fs (dm-0): mount failed The "get root inode failed" is rather unfortunate. Try running "debugfs /dev/dm0" and then use the "stat /" command. You

Hi again all, I apologize for not asking this in my first message; I just remembered the question after sending. On Sun, Jun 01, 2014 at 07:43:12PM -0700, Keith Keller wrote: > > On Sun, Jun 01, 2014 at 09:05:09PM -0400, Theodore Ts'o wrote: > > Unfortunately, there has been a huge number of bug fixes for ext4's > > online resize since 2.6.32 and 1.42.11. It's

* Keith Keller <kkeller@wombat.san-francisco.ca.us> hat geschrieben: Hi Keith > I have a very similar second server which has undergone a similar chain > of events, an initial ~2.5tb fs followed by a resize later. I believe > that it has been fsck'd since the resize (but don't quote me on that). > Am I likely to run into this issue with this fs? And if I do, what >

Hi all, On Mon, Jun 02, 2014 at 11:04:52PM +0200, Bodo Thiesen wrote: > > Keith is not the first one with problems of this class and he will > probably not be the last one. He later told us, that at first, mounting > the file system still worked. Is there any value in discussing this issue in keeping this broken filesystem available for debugging purposes? I would like at this